hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Juan Yu (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (HDFS-4324) Track and report out-of-date blocks separately from corrupt blocks
Date Thu, 10 Jul 2014 16:06:05 GMT

     [ https://issues.apache.org/jira/browse/HDFS-4324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Juan Yu reassigned HDFS-4324:
-----------------------------

    Assignee: Juan Yu

> Track and report out-of-date blocks separately from corrupt blocks
> ------------------------------------------------------------------
>
>                 Key: HDFS-4324
>                 URL: https://issues.apache.org/jira/browse/HDFS-4324
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: namenode
>    Affects Versions: 3.0.0
>            Reporter: Todd Lipcon
>            Assignee: Juan Yu
>
> Currently in various places (metrics, dfsadmin -report, fsck, logs) we use the term "corrupt"
to refer to blocks which have an out-of-date generation stamp. Since out-of-date blocks are
a fairly normal occurrence if a DN restarts while data is being written, we should be avoid
using 'scary' works like _corrupt_. This may need both some textual changes as well as some
internal changes to count the corruption types distinctly.



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

Mime
View raw message