You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Michael Han (JIRA)" <ji...@apache.org> on 2017/03/13 16:21:57 UTC

[jira] [Updated] (ZOOKEEPER-1768) Cluster fails election loop until the device is full

     [ https://issues.apache.org/jira/browse/ZOOKEEPER-1768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Han updated ZOOKEEPER-1768:
-----------------------------------
    Fix Version/s:     (was: 3.5.3)
                   3.5.4

> Cluster fails election loop until the device is full
> ----------------------------------------------------
>
>                 Key: ZOOKEEPER-1768
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1768
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: leaderElection
>    Affects Versions: 3.4.5
>            Reporter: yuxin.yan
>            Assignee: Flavio Junqueira
>             Fix For: 3.5.4, 3.6.0
>
>         Attachments: zk_debug.log.2013-09-25.log, zoo.cfg
>
>
> Hi, 
> I have a five nodes cluster versioned 3.4.5 and now i find one node is offline.
> Firstly i restart the node but i find that "Error contacting service. It is probably not running." and i find that the node always elect the leader and always sync the snapshot logs and the device will be full every ten mins. 
> so could someone help me? i will put the log and zoo.cfg in the attachment.
> Thanks all.
> yyx,



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)