[
https://issues.apache.org/jira/browse/ZOOKEEPER-1768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13791971#comment-13791971
]
Flavio Junqueira commented on ZOOKEEPER-1768:
---------------------------------------------
My interpretation of the problem is that syncing is taking too long. The one
problem we could consider fixing here, if I understand the issue right, is that
we delete the snapshot in the case the follower doesn't complete the sync. The
follower seems to be accumulating incomplete snapshots on disk, which
eventually makes the disk full.
We could consider it for 3.4.6, but it doesn't look like a blocker to me. Does
anyone disagree?
> 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)
