You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The ThresholdShedder load balance policy since Pulsar 2.6.0 by #6772. It can resolve many load balance issues of OverloadShedder and works well in many Pulsar production clusters.
In Pulsar 2.6.0, 2.7.0, 2.8.0 and 2.9.0, Pulsar's default load balance policy is OverloadShedder.
I think it's a good time for 2.10 to change default load balance policy to ThresholdShedder, it will make throughput more balance between brokers.
Proposed Changes
In 2.10 release,for broker.conf, change loadBalancerLoadSheddingStrategy from org.apache.pulsar.broker.loadbalance.impl.OverloadShedder to org.apache.pulsar.broker.loadbalance.impl.ThresholdShedder
The text was updated successfully, but these errors were encountered:
@rdhabalia The two load balance policy are has no state, and users can switch between them at any time. IMO, there is no incompatible issue for this change. Do you have any case for the compatible issue?
Motivation
The ThresholdShedder load balance policy since Pulsar 2.6.0 by #6772. It can resolve many load balance issues of
OverloadShedder
and works well in many Pulsar production clusters.In Pulsar 2.6.0, 2.7.0, 2.8.0 and 2.9.0, Pulsar's default load balance policy is
OverloadShedder
.I think it's a good time for 2.10 to change default load balance policy to
ThresholdShedder
, it will make throughput more balance between brokers.Proposed Changes
In 2.10 release,for
broker.conf
, changeloadBalancerLoadSheddingStrategy
fromorg.apache.pulsar.broker.loadbalance.impl.OverloadShedder
toorg.apache.pulsar.broker.loadbalance.impl.ThresholdShedder
The text was updated successfully, but these errors were encountered: