[
https://issues.apache.org/jira/browse/HDFS-3947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13459061#comment-13459061
]
Hadoop QA commented on HDFS-3947:
---------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12545507/HDFS-3947-b1.001.patch
against trunk revision .
-1 patch. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/3214//console
This message is automatically generated.
> If there are multiple edit logs with the same fstime, Recovery Mode should
> load a different one than the normal loading process
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: HDFS-3947
> URL: https://issues.apache.org/jira/browse/HDFS-3947
> Project: Hadoop HDFS
> Issue Type: Improvement
> Affects Versions: 1.2.0
> Reporter: Colin Patrick McCabe
> Assignee: Colin Patrick McCabe
> Priority: Minor
> Attachments: HDFS-3947-b1.001.patch
>
>
> If there are multiple edit logs with the same {{fstime}}, Recovery Mode
> should load a different one than the normal loading process. This will
> protect against many common kinds of corruption which affect only one edit
> log directory. For example, most I/O errors would fall into this category.
> This improvement is not necessary in branch-2 and later branches because in
> those branches, we have edit log failover (See HDFS-3049). However, this is
> an extremely simple and useful thing we can do to make Recovery Mode more
> helpful in branch-1.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
