oversearch commented on issue #19968: URL: https://github.com/apache/pulsar/issues/19968#issuecomment-1490576695
Thank you for the reply. I should have made it more clear in my original post, but I've verified that there are no connected consumers in any of the cases I've tested. The consumers are all self-contained in our integration test suite, which simply runs all of its tests and then exits. Afterwards those topics will never be touched again by producers or consumers. I've done some further testing, and it seems that if I restart the brokers and then publish to some of the topics to get them re-loaded in the topic cache, the message expiry will eventually kick in and clear them out. It's not clear to me if that's strictly necessary, or if the expiry just inexplicably takes a long time... I can see messages in the logs that seem to indicate that it's working, but in some cases the subscriptions are never expired and deleted. It's inconsistent, unfortunately, and I haven't been able to nail it down. In any case, allowing the thread which checks for expired topics/subscriptions/etc to load up inactive bundles and check them (even if done more sparingly) will fix most of this I think. -- 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]
