[I] [Bug] The UniformLoadShedder strategy fails when the broker magRate is less than 1000(delta) [pulsar]

["hanmz (via GitHub)" <gi...@apache.org>]

hanmz opened a new issue, #21905:
URL: https://github.com/apache/pulsar/issues/21905

   ### Search before asking
   
   - [X] I searched in the [issues](https://github.com/apache/pulsar/issues) and found nothing similar.
   
   
   ### Version
   
   3.0
   
   ### Minimal reproduce step
   
   The cluster configuration information is as follows(other load balacnce configurations remain at default values)：
   loadBalancerEnabled=true
   loadBalancerSheddingEnabled=true
   loadBalancerSheddingGracePeriodMinutes=5
   minUnloadMessage=0
   minUnloadMessageThroughput=0
   
   1、Start the first broker
   2、Create a multi-partition topic and distribute the partitions on different bundles
   3、Send messages to the topic at a speed less than 1000 TPS
   4、After waiting for the send to stabilize, start the second broker node
   5、Set loadBalancerSheddingEnabled=true
   
   ### What did you expect to see?
   
   The second broker is only allocated part of the traffic, and the traffic of the brokers is relatively balanced.
   
   ### What did you see instead?
   
   The second broker distributes all traffic.
   ![image](https://github.com/apache/pulsar/assets/16524922/e6bf6759-d516-448b-9302-c6aed97a223d)
   
   
   ### Anything else?
   
   _No response_
   
   ### Are you willing to submit a PR?
   
   - [X] I'm willing to submit a PR!


-- 
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: commits-unsubscribe@pulsar.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org