zookeeper-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steven Chan (Jira)" <j...@apache.org>
Subject [jira] [Created] (ZOOKEEPER-3556) Dynamic configuration file can not be updated automatically
Date Wed, 25 Sep 2019 07:06:00 GMT
Steven Chan created ZOOKEEPER-3556:
--------------------------------------

             Summary: Dynamic configuration file can not be updated automatically
                 Key: ZOOKEEPER-3556
                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3556
             Project: ZooKeeper
          Issue Type: Bug
          Components: java client
    Affects Versions: 3.5.5
            Reporter: Steven Chan


*I encountered 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.*

  *As far as I am concerned, the dynamic configuration file should be modified to this if
server 1 and server 5 are down suddenly as follows:*

  *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*

*But in this case, the dynamic configuration file will never change automatically unless you
manually revise it.*

  *I think this is a very common case which may happen at any time. If so, how can we handle
with it?*



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message