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

Tsz Wo (Nicholas), SZE commented on HDFS-3521:
----------------------------------------------

Hi Aaron,

Recovery mode in branch-1 just let you stop reading or quit without saving.  It 
does not really "recover" anything.  IMO, it does not seem useful.  How about 
we revert it?

Again, the edit log toleration can be disabled.  I think there is no reason to 
revert the patch.

If you see that other improvements could be made regarding to recovery mode or 
edit log toleration, we could discuss them in another JIRA.
                
> Allow namenode to tolerate edit log corruption
> ----------------------------------------------
>
>                 Key: HDFS-3521
>                 URL: https://issues.apache.org/jira/browse/HDFS-3521
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: name-node
>            Reporter: Tsz Wo (Nicholas), SZE
>            Assignee: Tsz Wo (Nicholas), SZE
>             Fix For: 1.2.0
>
>         Attachments: h3521_20120610_b-1.patch, h3521_20120611_b-1.0.patch, 
> h3521_20120611_b-1.patch
>
>
> HDFS-3479 adds checking for edit log corruption. It uses a fixed 
> UNCHECKED_REGION_LENGTH (=PREALLOCATION_LENGTH) so that the bytes at the end 
> within the length is not checked.  Instead of not checking the bytes, we 
> should check everything and allow toleration.

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