oneby-wang commented on issue #24879: URL: https://github.com/apache/pulsar/issues/24879#issuecomment-3445332871
> On partitions that didn't get any data, those topics are deleted right after the subscriptions are removed. You mean partitioned-topic with just one partition or non-partitioned topic? After my analysis, partitioned-topic with just one partition seems still has this problem. My analysis in case-0 is: broker0 called broker0 itself, but maxConnection is 1, then broker0 wait itself to release the the connection, the result is timeout. https://github.com/apache/pulsar/blob/313ae974ef01b7ed295a03c93906ccf9daf82fd5/pulsar-client-admin/src/main/java/org/apache/pulsar/client/admin/internal/http/AsyncHttpConnector.java#L149-L158 Call chain: 1. gc process -> 2. delete partitioned-topic admin api(called by broker0) -> 3. delete topic admin api(called by broker0). The concurrent race condition maybe another use case, so let' fix the self call problem first. BTW, I'll try to submit a PR to avoid the third admin api call if this analysis works. -- 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]
