Pulsar
3.0 introduces a new load manager implementation, aiming to balance cluster utilization as evenly as possible while minimizing latency and reducing reliance on ZooKeeper. The new load manager stores this load data in non-persistent topics, while topic ownership information is saved in system topics and maintained with a state machine for eventual consistency. Clients can now connect to any broker for lookup without redirection.
With the new Broker Load Balancer can improve the:
Pulsar 3.0 by default uses the previous ModularLoadManagerImpl
loadManagerClass and the new Load Balancer extra steps to manually enable.
Before using the new Load Balancer, please make sure upgrading the Pulsar to 3.0. Don’t recommand to upgrade Pulsar from 2.x and enable the the Load Balancer in the same process which may cause unexpected problems.
After your Pulsar is in 3.0, you can enable the new Load Balancer by adding the configuraitons under the PulsarBroker
CR:
Pulsar
3.0 introduces a new load manager implementation, aiming to balance cluster utilization as evenly as possible while minimizing latency and reducing reliance on ZooKeeper. The new load manager stores this load data in non-persistent topics, while topic ownership information is saved in system topics and maintained with a state machine for eventual consistency. Clients can now connect to any broker for lookup without redirection.
With the new Broker Load Balancer can improve the:
Pulsar 3.0 by default uses the previous ModularLoadManagerImpl
loadManagerClass and the new Load Balancer extra steps to manually enable.
Before using the new Load Balancer, please make sure upgrading the Pulsar to 3.0. Don’t recommand to upgrade Pulsar from 2.x and enable the the Load Balancer in the same process which may cause unexpected problems.
After your Pulsar is in 3.0, you can enable the new Load Balancer by adding the configuraitons under the PulsarBroker
CR: