You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@bookkeeper.apache.org by "Sijie Guo (JIRA)" <ji...@apache.org> on 2012/04/25 08:04:16 UTC

[jira] [Commented] (BOOKKEEPER-126) EntryLogger doesn't detect when one of it's logfiles is corrupt

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

Sijie Guo commented on BOOKKEEPER-126:
--------------------------------------

since the fsck like tool is planned to be added in 4.2.0, how about moving this task (including its sub-tasks BOOKKEEPER-199) from 4.1.0 to 4.2.0?
                
> EntryLogger doesn't detect when one of it's logfiles is corrupt
> ---------------------------------------------------------------
>
>                 Key: BOOKKEEPER-126
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-126
>             Project: Bookkeeper
>          Issue Type: Bug
>            Reporter: Ivan Kelly
>            Priority: Blocker
>             Fix For: 4.1.0
>
>
> If an entry log is corrupt, the bookie will ignore any entries past the corruption. Quorum writes stops this being a problem at the moment, but we should detect corruptions like this and rereplicate if necessary.

--
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