[
https://issues.apache.org/jira/browse/HDFS-7537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer updated HDFS-7537:
-----------------------------------
Description: 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. (was:
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.)
> 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
> 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)
