[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-1453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13408363#comment-13408363
 ] 

Flavio Junqueira commented on ZOOKEEPER-1453:
---------------------------------------------

I don't think the trace file is here, this is the output of ls after untaring 
it:

{noformat}
drwxr-xr-x  0 root   root        0 Jun 25 00:54 zookeeper/
-rw-r-----  0 root   root      247 Jun 25 01:12 zookeeper/10.10.5.123_2181.cfg
-rw-r-----  0 root   root      176 Jun 25 01:12 
zookeeper/10.10.5.123_2181.cfg.dynamic
-rw-r-----  0 root   root        1 Jun 25 01:12 zookeeper/myid
drwxr-xr-x  0 root   root        0 Jun 25 00:54 zookeeper/version-2/
-rw-r--r--  0 root   root        1 Jun 25 00:54 zookeeper/version-2/currentEpoch
-rw-r--r--  0 root   root        1 Jun 25 00:54 
zookeeper/version-2/acceptedEpoch
-rw-r--r--  0 root   root      669 Jun 25 00:54 zookeeper/version-2/snapshot.0
-rw-r--r--  0 root   root 67108880 Jun 25 01:09 
zookeeper/version-2/log.100000001
{noformat}

I was able to read the transaction log ok, though.
                
> 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: zookeeper.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

        

Reply via email to