Hi, Reconfiguration, as implemented, is not automatic. In your case, when failures happen, this doesn't change the ensemble membership. When 2 of 5 fail, this is still a minority, so everything should work normally, you just won't be able to handle an additional failure. If you'd like to remove them from the ensemble, you need to issue an explicit reconfiguration command to do so.
Please see details in the manual: https://zookeeper.apache.org/doc/r3.5.5/zookeeperReconfig.html Alex On Wed, Aug 21, 2019 at 7:29 AM Gao,Wei <wei....@arcserve.com> wrote: > Hi > I encounter a problem which blocks my development of load balance using > ZooKeeper 3.5.5. > Actually, I have a ZooKeeper cluster which comprises of five zk > servers. And the dynamic configuration file is as follows: > > server.1=zk1:2888:3888:participant;0.0.0.0:2181 > server.2=zk2:2888:3888:participant;0.0.0.0:2181 > server.3=zk3:2888:3888:participant;0.0.0.0:2181 > server.4=zk4:2888:3888:participant;0.0.0.0:2181 > server.5=zk5:2888:3888:participant;0.0.0.0:2181 > > The zk cluster can work fine if every member works normally. However, if > say two of them are suddenly down without previously being notified, > the dynamic configuration file shown above will not be synchronized > dynamically, which leads to the zk cluster fail to work normally. > I think this is a very common case which may happen at any time. If so, > how can we resolve it? > Really look forward to hearing from you! > Thanks >
