[
https://issues.apache.org/jira/browse/ZOOKEEPER-1453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13408956#comment-13408956
]
Marshall McMullen commented on ZOOKEEPER-1453:
----------------------------------------------
Two other observations about this massive roadblock that I've seen:
(1) Far, far more likely to be a problem if it's the leader node that is
rebooted
(2) Once rebooted, even if I clear out the version-2 directory and restart
zookeeper on that node it cannot rejoin the ensemble. If I restart one of the
other zookeeper processes that is already in the ensemble, then those *two
nodes* can now properly see one another and form quorum. The third node that
was already in the ensemble is suddenly not connectable. If I restart zookeeper
on that node, then it joins the new ensemble and everything is fine.
This seems pretty catastrophic to me.
> corrupted logs may not be correctly identified by FileTxnIterator
> -----------------------------------------------------------------
>
> Key: ZOOKEEPER-1453
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1453
> Project: ZooKeeper
> Issue Type: Bug
> Components: server
> Affects Versions: 3.3.3
> Reporter: Patrick Hunt
> Priority: Critical
> Attachments: 10.10.5.123-withPath1489.tar.gz, 10.10.5.123.tar.gz,
> 10.10.5.42-withPath1489.tar.gz, 10.10.5.42.tar.gz,
> 10.10.5.44-withPath1489.tar.gz, 10.10.5.44.tar.gz
>
>
> See ZOOKEEPER-1449 for background on this issue. The main problem is that
> during server recovery
> org.apache.zookeeper.server.persistence.FileTxnLog.FileTxnIterator.next()
> does not indicate if the available logs are valid or not. In some cases (say
> a truncated record and a single txnlog in the datadir) we will not detect
> that the file is corrupt, vs reaching the end of the file.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
