jsatterfield commented on issue #21082: URL: https://github.com/apache/pulsar/issues/21082#issuecomment-1751843893
Just started testing with Pulsar and ran into something that sounds like this. In my case, using `inactive_topic_policies.inactiveTopicDeleteMode: delete_when_subscriptions_caught_up` with partitioned topics, if my topic stops receiving new messages and my subscriptions hit 0 backlog, the topic partitions (`foo-partition-0`, `foo-partition-1`, etc) get deleted after the inactive time, along with the subscriptions to them. But the topic `foo` remains. When new messages are produced again, the topic partitions (`foo-partition-0`, `foo-parttiion-1`) are auto-created. The multi-topic consumer does not discover the newly recreated partitions. Fix was to add `autoUpdatePartitions` to my consumer config. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
