ntysdd opened a new issue #3226: Unclosed consumer after calling closeAsync URL: https://github.com/apache/pulsar/issues/3226 #### Expected behavior Consumer should be closed, and disappear in Pulsar Dashboard after we call closeAsync(). #### Actual behavior Consumer still there, and if we create a new consumer to the topic (same subscription shared mode), we see two (and more and more) consumers (with same addresses and ports) #### Steps to reproduce Create two consumers (maybe in different JVMs) in shared mode to the same topic. One of them called unsubscriptionAsync(), when the future failed, call closeAsync(), it will succeed, but the consumer will remain in the Dashboard (and pulsar admin stats). Then create a new consumer in that process, will see two consumers. #### System configuration **Pulsar version**: 2.2.0 Java version: 1.8 OS: Linux
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on 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
