Skip to content

[BUG] Judgment criteria for reconnecting the producer #13061

@wenbingshen

Description

@wenbingshen

Describe the bug
Related to this issue apache/pulsar-client-go#676

#11804, this PR rewrites the equals method of the Producer, resulting in that when different pulsar-client-go uses different port to reconnect, the old producer cannot be removed because the remoteAddress will be verified by equals:

if (producers.remove(producer.getProducerName(), producer)) {

#12846, this pr removes equals and will use hashcode for judgment. At this time, the
old producer cannot be removed.

The server does not allow different ports to connect to the same producerName. Does it assume that the previous connection will be disconnected first, and the new connection will be established? But the current pulsar-client-go seems to have some problems that the old connection did not handle.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions