hangc0276 commented on pull request #13204: URL: https://github.com/apache/pulsar/pull/13204#issuecomment-997125662
@gaozhangmin Thanks for your contribution. Before Pulsar 2.8.0, the broker publish throttle policy is similar to your implementation, it has a shortcoming of suddenly exceed the limit and will lead to broker direct memory OOM. After Pulsar 2.8.0, we introduced the throttle policy by io thread, it can limit the throughput of pulsar protocol, but out of control of other protocols, like KOP. IMO, it's better to throttle in KOP side, do you have any other ideas? @BewareMyPower -- 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]
