zookeeper-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Shraer (Jira)" <j...@apache.org>
Subject [jira] [Commented] (ZOOKEEPER-3556) Dynamic configuration file can not be updated automatically after some zookeeper servers of zk cluster are down
Date Wed, 25 Sep 2019 17:27:00 GMT

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-3556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16937925#comment-16937925
] 

Alexander Shraer commented on ZOOKEEPER-3556:
---------------------------------------------

The described behavior is not a bug – currently reconfiguration requires explicit action
by an operator. One could implement automation on top. We should consider this as a feature,
since it sounds like several adopters have implemented such automation. Perhaps one of them
could contribute this upstream.

> Dynamic configuration file can not be updated automatically after some zookeeper servers
of zk cluster are down
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: ZOOKEEPER-3556
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3556
>             Project: ZooKeeper
>          Issue Type: Wish
>          Components: java client
>    Affects Versions: 3.5.5
>            Reporter: Steven Chan
>            Priority: Major
>   Original Estimate: 12h
>  Remaining Estimate: 12h
>
> *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:*
>  ** 
> {color:#FF0000}  *server.1=zk1:2888:3888:participant;0.0.0.0:2181*{color}
> {color:#FF0000}  *server.2=zk2:2888:3888:participant;0.0.0.0:2181*{color}
> {color:#FF0000}  *server.3=zk3:2888:3888:participant;0.0.0.0:2181*{color}
> {color:#FF0000}  *server.4=zk4:2888:3888:participant;0.0.0.0:2181*{color}
> {color:#FF0000}  *server.5=zk5:2888:3888:participant;0.0.0.0:2181*{color}
>  ** 
>   *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:*
> {color:#FF0000}  *server.2=zk2:2888:3888:participant;0.0.0.0:2181*{color}
> {color:#FF0000}  *server.3=zk3:2888:3888:participant;0.0.0.0:2181*{color}
> {color:#FF0000}  *server.4=zk4:2888:3888:participant;0.0.0.0:2181*{color}
> *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