Jumping in to this conversation:
I know that's best practice. In my case though, we have a situation where we
spread our zk nodes across two networks in different buildings connected with
high speed robust, redundant networks. We also have some servers at a third
co-location facility is
I also don't really know why you would need a single host being "preferred"
as leader. I think the safest (and the best practice) is to make sure all
your ZooKeeper servers are the same in terms of networking / performance /
etc.
Not knowing your goals, maybe the Observer feature is also
George,
really, it should not be a problem which is the leader. it is
automatically chosen.
Each node should be ideally as powerful as the other peers.
why do you need this "preferred leader" ?
I am afraid that you have some flaw in your design
Enrico
Il giorno lun 20 giu 2022 alle ore 05:39
Hi,
I think this could be achieved with help from `reconfig`[1]:
* Configs all nodes with `standaloneEnabled=false`, `reconfigEnabled=true`.
* Starts node-2 as sole quorum participant.
* Now node-2 is the leader. You will see "No server failure will be
tolerated. You need at least 3 servers”.
*
We have 3 Zookeeper nodes and would like node 2 to always be the leader unless
node 2 goes down. IF node 2 goes down, then either node 1 or node 3 would be
the leader.
Can this be done? If so, how would this be done?
smime.p7s
Description: S/MIME cryptographic signature
We have 3 Zookeeper nodes and would like node 2 to always be the leader unless
node 2 goes down. IF node 2 goes down, then either node 1 or node 3 would be
the leader.
Can this be done? If so, how would this be done?
smime.p7s
Description: S/MIME cryptographic signature
