Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Thu, 18 Dec 2014 22:04:14 +0000 (UTC)
From: "Allen Wittenauer (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12762132.1418768072000.61944.1418940254625@Atlassian.JIRA>
In-Reply-To: <JIRA.12762132.1418768072000@Atlassian.JIRA>
References: <JIRA.12762132.1418768072000@Atlassian.JIRA>
 <JIRA.12762132.1418768072326@arcas>
Subject: [jira] [Updated] (HDFS-7537) dfs.namenode.replication.min > 1 &&
 missing replicas && NN restart is confusing
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HDFS-7537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Allen Wittenauer updated HDFS-7537:
-----------------------------------
    Attachment: dfs-min-2.png

> 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
>         Attachments: 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)