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] [Commented] (HDFS-9959) add log when block removed from last live datanode
Date Mon, 14 Mar 2016 21:49:34 GMT

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

Tsz Wo Nicholas Sze commented on HDFS-9959:
-------------------------------------------

For recovering blk_1073741825, we may search other logs for it to find out all the locations.
 Do we really need this new message?

BTW, the new message is printed within the write lock.  So, it has performance penalty.

> 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
>            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