[
https://issues.apache.org/jira/browse/HDFS-7537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14338451#comment-14338451
]
Hudson commented on HDFS-7537:
------------------------------
FAILURE: Integrated in Hadoop-Hdfs-trunk-Java8 #107 (See
[https://builds.apache.org/job/Hadoop-Hdfs-trunk-Java8/107/])
HDFS-7537. Add "UNDER MIN REPL'D BLOCKS" count to fsck. Contributed by GAO Rui
(szetszwo: rev 725cc499f00abeeab9f58cbc778e65522eec9d98)
*
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/NamenodeFsck.java
*
hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestFsck.java
* hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
> 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
> Fix For: 2.7.0
>
> 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)
