oneby-wang commented on issue #24879: URL: https://github.com/apache/pulsar/issues/24879#issuecomment-3449267719
> Do you have a suggestion about `brokerClient_connectionsPerBroker`? My suggestion: 1. `brokerClient_connectionsPerBroker=0` is ok if you are not so care about performance. I read through the code and find adminClient in pulsar broker usages are very limited, with a relatively low call frequency in background. Unpooled means new tcp connection in every admin api call. 2. If you want to use adminClient connection pool, just tune `brokerClient_connectionsPerBroker` into a bigger value. A few more connections in NIO programming won't affects performance too much. And `brokerClient_connectionsPerBroker=n` is just a safe value. If there are m partitions in a partitioned-topic calling the delete partitioned-topic Admin API simultaneously(race condition), you only need to ensure that `brokerClient_connectionsPerBroker` > m. > but for these 2 days, I've having seen the http timeouts or orphaned topics. A little bit confused, so the `brokerClient_connectionsPerBroker` works for you or not? What cases will cause http timeouts or orphaned topics? > I have done this in previous cases of dirty topic deletions, and sometimes it has told me "No such topic" indicating corruption somewhere in the metadata or overall tracking of the topic. If you encounter this again, please provide some logs. I think `pulsar-admin topics delete-partitioned-topic` should be an idempotent operation. -- 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]
