galrose opened a new issue #10382: URL: https://github.com/apache/pulsar/issues/10382
**Describe the bug** When using the pulsar-perf and writing messages either in large batches (>100) or large number of outstanding messages (>100). When limiting either the -bm or -o to a small number around 5, preferably 1 it works perfectly. The easiest way to check is not setting the -bm or -o in pulsar-perf. Slack thread: https://apache-pulsar.slack.com/archives/C5Z4T36F7/p1619419736156600?thread_ts=1619419736.156600&cid=C5Z4T36F7 **To Reproduce** Steps to reproduce the behavior: 1. preciseTopicPublishRateLimiterEnable=true in the broker.conf 2. Create a new tenant, namespace, and topic. 3. Run 'pulsar-admin namespaces set-publish-rate mytenant/default -b 102400' 4. Run 'pulsar-perf produce -s 1024 -threads 1 -r 1000' 5. You can see both in the metrics and in the pulsar-perf that the rate is not limited precisely. **Expected behavior** I expect the limit to be precise no matter the batch or outstanding messages. **Desktop (please complete the following information):** - OS: Centos 7 -- 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]
