Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-dev@hadoop.apache.org
Date: Mon, 29 Sep 2014 21:33:34 +0000 (UTC)
From: "Andrew Wang (JIRA)" <jira@apache.org>
To: hdfs-dev@hadoop.apache.org
Message-ID: <JIRA.12744792.1412026408000.149185.1412026414365@Atlassian.JIRA>
In-Reply-To: <JIRA.12744792.1412026408000@Atlassian.JIRA>
References: <JIRA.12744792.1412026408000@Atlassian.JIRA>
 <JIRA.12744792.1412026408216@arcas>
Subject: [jira] [Created] (HDFS-7165) Separate block metrics for files with
 replication count 1
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Andrew Wang created HDFS-7165:
---------------------------------

             Summary: Separate block metrics for files with replication count 1
                 Key: HDFS-7165
                 URL: https://issues.apache.org/jira/browse/HDFS-7165
             Project: Hadoop HDFS
          Issue Type: Improvement
    Affects Versions: 2.5.1
            Reporter: Andrew Wang


We see a lot of escalations because someone has written teragen output with a replication factor of 1, a DN goes down, and a bunch of missing blocks show up. These are normally false positives, since teragen output is disposable, and generally speaking, users should understand this is true for all repl=1 files.

It'd be nice to be able to separate out these repl=1 missing blocks from missing blocks with higher replication factors..


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)