GitHub user rillo-carrillo created a discussion: Zookeeper lose cluster information
I have a zookeeper cluster on kubernetes. Each zookeeper has it's own persistent storage. Once zookeeper cluster is enabled I execute initialize-cluster-metadata command: ``` pulsar initialize-cluster-metadata --cluster pulsardev \ --zookeeper zookeeper-0.zookeepers:2181,zookeeper-1.zookeepers:2181,zookeeper-2.zookeepers:2181 \ --configuration-store zookeeper-0.zookeepers:2184,zookeeper-1.zookeepers:2184,zookeeper-2.zookeepers:2184 \ --web-service-url http://broker-0.brokers:8080,broker-1.brokers:8080,broker-2.brokers:8080 \ --web-service-url-tls https://broker-0.brokers:8443,broker-1.brokers:8443,broker-2.brokers:8443 \ --broker-service-url pulsar://broker-0.brokers:6650,broker-1.brokers:6650,broker-2.brokers:6650 \ --broker-service-url-tls pulsar+ssl://broker-0.brokers:6651,broker-1.brokers:6651,broker-2.brokers:6651 ``` After executing I can see multiple paths created on zk ``` / zookeeper stream bookies ledgers pulsar ``` So far so good, but If for some reason I update some configuration on pulsar image and update happens with the RollingUpdate strategy the paths I previously saw are "lost", now I can only see: ``` / admin zookeeper ``` Is there any way to avoid such behaviour? GitHub link: https://github.com/apache/pulsar/discussions/17286 ---- This is an automatically sent email for dev@pulsar.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@pulsar.apache.org
