You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2021/12/08 12:42:45 UTC

[GitHub] [pulsar] suiyuzeng commented on issue #13119: Load balance shedding not in time with the strategy of ThresholdShedder

suiyuzeng commented on issue #13119:
URL: https://github.com/apache/pulsar/issues/13119#issuecomment-988778352


   > @suiyuzeng @hangc0276 I met this problem too. One way to reduce the time for load balance is to set the value of `loadBalancerHistoryResourcePercentage` to a lower value, for example, 0.5 instread of the default 0.9.
   
   It will work for this issue. But some time, we may need a high percentage of the history.
   I think the threshold strategy should recorder the history even if the leader change. How about this way:
   1. store the history in zk.
   2. if a broker restart, discard the history. If the czxid of the broker in ledger/available change,  discard the history.
   
   @hangc0276 @Jason918 


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

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