[
https://issues.apache.org/jira/browse/HDFS-7537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14336110#comment-14336110
]
GAO Rui commented on HDFS-7537:
-------------------------------
I have attached a new patch which added
DFSConfigKeys.DFS_NAMENODE_REPLICATION_MIN_KEY to the output of fsck and made a
unit test to confirm this change. Please review that when you are free, thanks
a lot.
> 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,
> 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)
