[
https://issues.apache.org/jira/browse/HDFS-7537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14337685#comment-14337685
]
Hadoop QA commented on HDFS-7537:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12700935/Screen%20Shot%202015-02-26%20at%2010.30.35.png
against trunk revision d140d76.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/9670//console
This message is automatically generated.
> fsck is confusing when dfs.namenode.replication.min > 1 && missing replicas
> && NN restart
> -----------------------------------------------------------------------------------------
>
> Key: HDFS-7537
> URL: https://issues.apache.org/jira/browse/HDFS-7537
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: namenode
> Reporter: Allen Wittenauer
> Assignee: GAO Rui
> Attachments: HDFS-7537.1.patch, HDFS-7537.2.patch, Screen Shot
> 2015-02-26 at 10.27.46.png, Screen Shot 2015-02-26 at 10.30.35.png,
> dfs-min-2-fsck.png, dfs-min-2.png
>
>
> If minimum replication is set to 2 or higher and some of those replicas are
> missing and the namenode restarts, it isn't always obvious that the missing
> replicas are the reason why the namenode isn't leaving safemode. We should
> improve the output of fsck and the web UI to make it obvious that the missing
> blocks are from unmet replicas vs. completely/totally missing.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
