alexku7 commented on issue #9585: URL: https://github.com/apache/pulsar/issues/9585#issuecomment-786162631
> > If the consumer is multiple topic consumer, only part of the topics been removed, the correct behavior is one part of the internal consumer been closed with an exception, others should continue works(such as you subscribe to topic-a topic-b topic-c), If topic-a removed, the consume should continue to consume messages from topic-b topic-c. But if topic-b topic-b been removed, the consumer should be closed. > > In the case of multi-topics, actually, if you delete the whole topic, hence all its partitions, the consumer does not close. **The partitions' consumers are closed but kept in the root consumer list.** Thus my PR #9660 updates this list automatically so the closed ones are dropped and new consumers are created when the topic is created again. @codelipenghui In my case I observed the same behavior. I delete multi partioned topic and create the same topic again after , let's say half minute. The client remained in kind of "hang" state and doesn't reconnect again. We should restart the client completely in order to reconnect, which is not always convenient . We tried to catch this event in the code and re- create the client again in the code without restart the executable but we simply can't do it , because can"t get any exception or other indicator that could allow us to handle this situation inside the code without restart the client ---------------------------------------------------------------- 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]
