rdhabalia commented on pull request #7499: URL: https://github.com/apache/pulsar/pull/7499#issuecomment-930630840
We have added this PR #7499 patch in internally and was working fine but after upgrading pulsar version and without this change our broker again started crashing. The main issue with #7406 which I mentioned in previous comment as well that it distributes max global bytes across separate IO threads which has its own disadvantage eg: 1gb across 30 IO threads means 1 IO thread can only do 33MB it means as a user I have to create multiple connections and hope it will be served by other IO thread to get higher throughput. In multi-tenant environment , this issue will be really painful when a critical user starts facing high latency due per thread bottleneck even though broker has resources but distributed to other threads and at that time we have to manually unload topics at server side to spread new connections across different threads and wait to be lucky for uniform cnx distribution. #7406 is doesn't make our life easy when we are managing pulsar in multi-tenant environment. -- 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]
