hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Akira AJISAKA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-6682) Add a metric to expose the timestamp of the oldest under-replicated block
Date Wed, 29 Jul 2015 07:45:06 GMT

    [ https://issues.apache.org/jira/browse/HDFS-6682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14645638#comment-14645638
] 

Akira AJISAKA commented on HDFS-6682:
-------------------------------------

bq. -1 for the patch. Sorry I come late. Akira AJISAKA, could we revert it?
Agree that this patch affects performance. I'll revert it.

bq. On the other hand, honestly I don't see real value of adding this metric. The disadvantage
is much larger than the benefit from my point of view
Do you have any idea to deal with the issue in the description instead of using the metric?

> 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
>             Fix For: 2.8.0
>
>         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)

Mime
View raw message