Return-Path: X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A7DD910C13 for ; Fri, 13 Feb 2015 22:26:12 +0000 (UTC) Received: (qmail 7431 invoked by uid 500); 13 Feb 2015 22:26:12 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 7372 invoked by uid 500); 13 Feb 2015 22:26:12 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-issues@hadoop.apache.org Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 7361 invoked by uid 99); 13 Feb 2015 22:26:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Feb 2015 22:26:12 +0000 Date: Fri, 13 Feb 2015 22:26:12 +0000 (UTC) From: "Tsz Wo Nicholas Sze (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HDFS-7537) fsck is confusing when dfs.namenode.replication.min > 1 && missing replicas && NN restart MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HDFS-7537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze updated HDFS-7537: -------------------------------------- Summary: fsck is confusing when dfs.namenode.replication.min > 1 && missing replicas && NN restart (was: dfs.namenode.replication.min > 1 && missing replicas && NN restart is confusing) > 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 > Reporter: Allen Wittenauer > Attachments: 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)