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 Tue, 22 Mar 2016 19:51:25 GMT

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

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

The new patch looks great! Thanks for adding a test. One minor comment:

- Instead of DatanodeID, let's pass Object in log(DatanodeID dn), i.e. log(Object name). 
Then, we could just pass failedStorage, i.e. BlocksMap.MissingBlockLog.log(failedStorage).
 Otherwise, users may be confused by the warning message since the datanode is still running
for the failed storage case.

> 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.1.patch, HDFS-9959.2.patch, HDFS-9959.3.patch, HDFS-9959.3.withtest.patch,
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