anvinjain commented on issue #11044: URL: https://github.com/apache/pulsar/issues/11044#issuecomment-866709447
One way to fix this could to be penalize subsequent rate period too if we have gone over the limit in one of the period (in this case period = 1 second). Another way would be to calculate messagesToRead proportionally according to byte limit. In fact this is even done here: https://github.com/apache/pulsar/blob/b9db969d6bc3e2d18ee35e84629c6634560fb622/managed-ledger/src/main/java/org/apache/bookkeeper/mledger/impl/ManagedCursorImpl.java#L3004 but here maxSizeBytes is coming from dispatcherMaxReadSizeBytes and not from the dispatch limit which user has configured. -- 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. For queries about this service, please contact Infrastructure at: [email protected]
