315157973 commented on issue #18128: URL: https://github.com/apache/pulsar/issues/18128#issuecomment-1305073899
> I am not sure exactly how the zombie topics come from, but from this description, the number may be accumulated for a long time with old clusters. Once user upgraded to a version with this feature, they may need to cleanup a large number of these topics at the first time. > > From what I see, the total time required to do the cleanup work does not matter that much, maybe even single thread is good enough. But we need to minimize the impact on the server stability. The scene where the zombie topic appears: 1) Some businesses try out some topics, but they haven't used this topic since then 2) Some topics that have data but have not been used since then, and they have not been deleted The current `TrimLedger` is to concurrently traverse the Topics in memory and clean up all Topics. Do you mean that this parallel cleanup will also affect the stability of the Broker, so it need a single thread? I will modify current `TrimLedger` and add a single-thread thread pool to queue these tasks. -- 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]
