You are viewing a plain text version of this content. The canonical link for it is here.

Posted to hdfs-issues@hadoop.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2014/12/16 23:15:14 UTC

[jira] [Created] (HDFS-7537) dfs.namenode.replication.min > 1 && missing replicas && NN restart is confusing

Allen Wittenauer created HDFS-7537:
--------------------------------------

             Summary: dfs.namenode.replication.min > 1 && missing replicas && NN restart is confusing
                 Key: HDFS-7537
                 URL: https://issues.apache.org/jira/browse/HDFS-7537
             Project: Hadoop HDFS
          Issue Type: Improvement
            Reporter: Allen Wittenauer


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