You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Cristina Groapa (JIRA)" <ji...@apache.org> on 2015/12/07 16:51:11 UTC
[jira] [Commented] (ZOOKEEPER-1453) corrupted logs may not be
correctly identified by FileTxnIterator
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15045108#comment-15045108 ]
Cristina Groapa commented on ZOOKEEPER-1453:
--------------------------------------------
Hi Bill, is there any progress being done on this issue? I saw some talk of a new Jira to handle corruption - is that still intended?
My team has recently started to use zookeeper. We had an incident where we couldn't restart a node without deleting its logs.
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)