[ https://issues.apache.org/jira/browse/ZOOKEEPER-1453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13408707#comment-13408707 ]
Marshall McMullen commented on ZOOKEEPER-1453: ---------------------------------------------- Can anyone explain two things in the above that are really puzzling to me: (1) Why does it continually show "ZooKeeperServer not running" ? I am certain the *process* is running. So this must not refer to the process itself but something else. Can someone explain? (2) What does this message signify: 2012-07-07 10:20:23,342 [myid:2] - INFO [WorkerSender[myid=2]:QuorumCnxManager@191] - Have smaller server identifier, so dropping the connection: (3, 2) > 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