zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "BigYang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ZOOKEEPER-2855) Rebooting a Joined Node Failed Due The Joined Node Previously Failed to Update Its Configuration Correctly
Date Mon, 30 Oct 2017 12:59:00 GMT

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

BigYang commented on ZOOKEEPER-2855:
------------------------------------

  I encountered the same problem.  I have 3 nodes, and 4th node add as observer.  I use zkCli.sh
reconfig command add success.
but the files of  4th node's conf dir is here:
-rw-r--r-- 1 root staff  535 Oct 30 20:12 configuration.xsl
-rw-r--r-- 1 root staff 2717 Oct 30 20:12 log4j.properties
-rw-r--r-- 1 root staff  268 Oct 30 20:12 zoo.cfg
-rw-r--r-- 1 root staff  253 Oct 30 20:12 zoo.cfg.dynamic
-rw-r--r-- 1 root staff  197 Oct 30 20:12 zoo.cfg.dynamic.10000066d
-rw-r--r-- 1 root staff  278 Oct 30 20:12 zoo.cfg.dynamic.next

In some reason, i can't upload the debug log. 

> Rebooting a Joined Node Failed Due The Joined Node Previously Failed to Update Its Configuration
Correctly
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: ZOOKEEPER-2855
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2855
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: leaderElection, quorum, server
>    Affects Versions: 3.5.3
>            Reporter: Jeffrey F. Lukman
>            Assignee: Alexander Shraer
>         Attachments: ZK-2855.pdf
>
>
> We are testing our distributed system model checking (DMCK)
> by directing our DMCK to reproduce the ZooKepeer-2172 bug in the ZooKeeper v3.5.3.
> After some exploration, our DMCK found that the ZooKeeper-2172 still linger in the reported
fixed version, ZooKeeper v.3.5.3.
> Here we attached the complete bug scenario to reproduce the bug.
> We have communicated this bug to [~shralex] and he has confirmed that this bug exists.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message