One doubt about it: In order to have a highly available zookeeper, you must have at least three separate physical servers for ZK. Running multiple zookeepers on one physical machine gains you nothing ... because if the whole machine fails, you lose all of those zookeepers. If you have three physical servers, one can fail with no problems. If you have five separate physical servers running ZK, then two of the machines can fail without taking the cluster down.
If I'm not mistaken the number of zookeepers must be odd. Having 3 zoos on 3 different machines, if we temporarily lost one of the three machines, we would have only two running and it would be an even number.Would it be advisable in this case to raise a third party in one of the 2 active machines or with only two zookeepers there would be no blockages in their internal votes? About the dynamic reconfiguration many thanks we've 8.2 but the zoos are in 3.4.2 version, we're going to test with 3.5 version and the dynamic configuration of zookeepers to avoid this problem. Many thanks. Kind regards. ________________________________ De: Joe Lerner <joeler...@gmail.com> Enviado: viernes, 19 de febrero de 2021 18:56 Para: solr-user@lucene.apache.org <solr-user@lucene.apache.org> Asunto: Re: Dynamic starting or stoping of zookeepers in a cluster This is solid information. *How about the application, which uses SOLR/Zookeeper?* Do we have to follow this guidance, to make the application ZK config aware: https://zookeeper.apache.org/doc/r3.5.5/zookeeperReconfig.html#ch_reconfig_rebalancing <https://zookeeper.apache.org/doc/r3.5.5/zookeeperReconfig.html#ch_reconfig_rebalancing> Or, could we leave it as is, and as long as the ZK Ensemble has the same IPs? Thanks! Joe -- Sent from: https://lucene.472066.n3.nabble.com/Solr-User-f472068.html
