hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tsz Wo Nicholas Sze (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (HDFS-9959) add log when block removed from last live datanode
Date Tue, 15 Mar 2016 01:08:33 GMT

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

Tsz Wo Nicholas Sze edited comment on HDFS-9959 at 3/15/16 1:07 AM:
--------------------------------------------------------------------

> ... In real production cluster, this should not happen often, otherwise there will be
lots of corrupt files.

This is based on assumptions that the cluster is well managed and the users are not creating
single replica files.  These assumptions may not be true, unfortunately.


was (Author: szetszwo):
> ... In real production cluster, this should not happen often, otherwise there will be
lots of corrupt files.

This is based on assumptions that the cluster is well managed and the users are not creating
single replica files.  The assumptions may not be true.

> add log when block removed from last live datanode
> --------------------------------------------------
>
>                 Key: HDFS-9959
>                 URL: https://issues.apache.org/jira/browse/HDFS-9959
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: namenode
>            Reporter: yunjiong zhao
>            Assignee: yunjiong zhao
>            Priority: Minor
>         Attachments: HDFS-9959.patch
>
>
> Add logs like "BLOCK* No live nodes contain block blk_1073741825_1001, last datanode
contain it is node: 127.0.0.1:65341" in BlockStateChange should help to identify which datanode
should be fixed first to recover missing blocks.



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

Mime
View raw message