Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Tue, 15 Jul 2014 08:17:04 +0000 (UTC)
From: "Akira AJISAKA (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12727285.1405412196494.43327.1405412224503@arcas>
In-Reply-To: <JIRA.12727285.1405412196494@arcas>
References: <JIRA.12727285.1405412196494@arcas>
Subject: [jira] [Created] (HDFS-6682) Add a metric to expose the timestamp
 of the oldest under-replicated block
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Akira AJISAKA created HDFS-6682:
-----------------------------------

             Summary: Add a metric to expose the timestamp of the oldest under-replicated block
                 Key: HDFS-6682
                 URL: https://issues.apache.org/jira/browse/HDFS-6682
             Project: Hadoop HDFS
          Issue Type: Improvement
            Reporter: Akira AJISAKA
            Assignee: Akira AJISAKA


In the following case, the data in the HDFS is lost and a client needs to put the same file again.
# A Client puts a file to HDFS
# A DataNode crashes before replicating a block of the file to other DataNodes

I propose a metric to expose the timestamp of the oldest under-replicated/corrupt block. That way client can know what file to retain for the re-try.


--
This message was sent by Atlassian JIRA
(v6.2#6252)