darinspivey commented on issue #24879: URL: https://github.com/apache/pulsar/issues/24879#issuecomment-3448840273
As you said, yes, it feels like there could be several things going on, so one thing at a time. After 2 days of monitoring, I see that adding `brokerClient_connectionsPerBroker=10` *might* have been helping. I've now seen 2 days of topics getting deleted cleanly (we have a nightly test suite that creates lots of topics which are then deleted the next day by GC--this is how I've been watching). That's great, but I don't want to call it fixed just yet, but for these 2 days, I've having seen the http timeouts or orphaned topics. To be clear, if `0` is used for that value, it does no connection pooling? We could have topics that have 15 partitions in the future, so I'd rather not have it be a static value too low. On the other hand, turning off pooling sounds like a bad idea. Do you have a suggestion there, or can it be something like `20` (which I doubt we'd ever get a topic with that many partitions)? Your analysis of case0 is interesting--I'm glad you see something to work with there. I'll watch for more cases and post them if there are any. Thanks! -- 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]
