sn-platform
1.11 uses the Pulsar
3.0 as the default which 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:
ModularLoadManagerImpl
loadManagerClass and the new Load Balancer extra steps to manually enable.
helm upgrade
process which may cause unexpected problems.broker.configData
field in the helm values. And use the helm upgrade
command to update the configuration.