On 25 June 2015 at 19:23, Alexander Shraer <[email protected]> wrote: > > A Group Communication / Virtual Synchrony may be better suited here. In > Paxos-based systems > you need a majority of the servers to remain connected to have progress. It > tolerates a minority being > offline but stops working once you have more failures / disconnects. You > could reconfigure > to remove someone from the cluster when he is suspected (otherwise you risk > remaining without a quorum). > With group communication / virtual synchrony reconfiguration happens > automatically when a server > leaves and it gives you primitives to communicate with members of the > current group, such as atomic broadcast > (equivalent to consensus). You can achieve the same with ZK, but it may be > more work (I'm not sure). > > Check out Isis2 from (Ken Birman's project), Ensemble group communication, > JGroups and others.
Or, if you are running 3.5 (or later) you could run this command [0] from your shutdown scripts to remove each server as they go away: zk-shell --run-once 'reconfig remove 7' localhost -rgs [0] https://github.com/rgs1/zk_shell
