Demogorgon314 commented on issue #15905:
URL: https://github.com/apache/pulsar/issues/15905#issuecomment-1158581682

   > "The weights for each resource are configurable." - it would be great if 
the weights were listed or perhaps a link to the relevant section of the 
reference configuration here 
https://pulsar.apache.org/docs/reference-configuration/#broker
   
   You can see these configurations.
   ```
   # The BandWithIn usage weight when calculating new resource usage.
   # It only takes effect in the ThresholdShedder strategy.
   loadBalancerBandwithInResourceWeight=1.0
   
   # The BandWithOut usage weight when calculating new resource usage.
   # It only takes effect in the ThresholdShedder strategy.
   loadBalancerBandwithOutResourceWeight=1.0
   
   # The CPU usage weight when calculating new resource usage.
   # It only takes effect in the ThresholdShedder strategy.
   loadBalancerCPUResourceWeight=1.0
   
   # The heap memory usage weight when calculating new resource usage.
   # It only takes effect in the ThresholdShedder strategy.
   loadBalancerMemoryResourceWeight=1.0
   
   # The direct memory usage weight when calculating new resource usage.
   # It only takes effect in the ThresholdShedder strategy.
   loadBalancerDirectMemoryResourceWeight=1.0
   ```
   
   > "If a broker's usage is greater than the average usage per broker plus the 
loadBalancerBrokerThresholdShedderPercentage"
   Is that percentage an absolute percentage?
   
   It should be an absolute percentage.
   
   Example:
   Assume we have three brokers, the broker1 avg broker usage is 40%, the 
broker2 avg broker usage is 10%, the broker3 avg broker usage is 10%, then the 
cluster avg usage should be ((40% + 10% + 10%) / 3) = 20%.
   
   If we set `loadBalancerBrokerThresholdShedderPercentage=1`, then the 
broker1's some bundles will get unloaded, because broker1 broker avg usage is 
greater than cluster avg usage plus 
loadBalancerBrokerThresholdShedderPercentage.
   
   


-- 
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]

Reply via email to