[
https://issues.apache.org/jira/browse/HDFS-6682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14646290#comment-14646290
]
Hudson commented on HDFS-6682:
------------------------------
SUCCESS: Integrated in Hadoop-Mapreduce-trunk #2217 (See
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/2217/])
Revert "HDFS-6682. Add a metric to expose the timestamp of the oldest
under-replicated block. (aajisaka)" (aajisaka: rev
2a1d656196cf9750fa482cb10893684e8a2ce7c3)
*
hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/blockmanagement/TestUnderReplicatedBlocks.java
*
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/blockmanagement/BlockManager.java
*
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/blockmanagement/UnderReplicatedBlocks.java
*
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSNamesystem.java
* hadoop-common-project/hadoop-common/src/site/markdown/Metrics.md
* hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
> 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
> Labels: metrics
> Attachments: HDFS-6682.002.patch, HDFS-6682.003.patch,
> HDFS-6682.004.patch, HDFS-6682.005.patch, HDFS-6682.006.patch, HDFS-6682.patch
>
>
> 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.3.4#6332)
