f-ld commented on issue #5104: Handle already have connected replicate produce with same name URL: https://github.com/apache/pulsar/issues/5104#issuecomment-542688330 In my previous messages I mixed things a bit (because I am discovering things at the same time). This: ``` 10:21:58.694 [pulsar-io-22-13] INFO org.apache.pulsar.client.impl.ProducerImpl - [persistent://tenant/namespace/topic-partition-1] [pulsar.repl.region3] Creating producer on cnx [id: 0x581a0460, L:/10.12.3.213:43308 - R:10.10.3.46/10.10.3.46:6650] ``` does not mean that the broker is not seeing the connection but it means that the broker is creating the producer on a connection from its pool. So the connection exists (and this is what we see on both brokers). I also mixed two connections on port 43300 and 43308. Indeed, there is another connection between the two above brokers: - region1: ``` tcp 0 0 10.10.3.46:6650 10.12.3.213:43308 ESTABLISHED 11/java ``` - region3: ``` tcp 0 0 10.12.3.213:43308 10.10.3.46:6650 ESTABLISHED 11/java ``` So now trying to find out how I can see/reset producers on broker side and what happened exactly to get that inconsistent status / if there is a configuration that would help avoiding it
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
