[I] Race during reonnect [pulsar-client-go]

["Gilthoniel (via GitHub)" <gi...@apache.org>]

Gilthoniel opened a new issue, #1274:
URL: https://github.com/apache/pulsar-client-go/issues/1274

   #### Expected behavior
   
   After reconnecting to the broker, a consumer or a producer should register itself for callbacks.
   
   #### Actual behavior
   
   After reconnecting to the broker, a consumer attempts to add itself before the connection is closed then attempts to lock the list of handlers. The connection gets closed at that moment and wins the race against the lock, removes the listeners and closes. Then the consumer adds the listener and considers itself ready.
   
   #### Steps to reproduce
   
   I could observe this behavior in a cluster considered not ready as it was restarting. After the application reconnected, one reader was considered ok and was waiting for messages while it was actually not registered in the topic.
   
   #### System configuration
   **Pulsar version**: v3.0.5
   **Pulsar client**: v13.1
   


-- 
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.

To unsubscribe, e-mail: commits-unsubscribe@pulsar.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [I] Race during reconnect [pulsar-client-go]

["nodece (via GitHub)" <gi...@apache.org>]

nodece closed issue #1274: Race during reconnect
URL: https://github.com/apache/pulsar-client-go/issues/1274


-- 
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.

To unsubscribe, e-mail: commits-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org