[
https://issues.apache.org/jira/browse/ZOOKEEPER-1768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13792184#comment-13792184
]
yuxin.yan commented on ZOOKEEPER-1768:
--------------------------------------
Flavio Junqueira, thank you for your explanation. I agree with you. Here is the
detail after the node was dead: firstly, i found the disk is full the next
day(is it important for my case?), then i just restarted the node, then i found
that couse of "
autopurge.snapRetainCount=10
autopurge.purgeInterval=24
" configuration in the zoo.cfg, the node removed the other snapshots and
transaction logs, then it started failure("Error contacting service. It is
probably not running."), means it always wanted to sync to leader and recreate
new snapshots, then the disk was full again.
> 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
> Fix For: 3.4.6, 3.5.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.1#6144)
