[
https://issues.apache.org/jira/browse/HDFS-9959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15194351#comment-15194351
]
yunjiong zhao commented on HDFS-9959:
-------------------------------------
If removeNode(Block b, DatanodeDescriptor node) was invoked by
DatanodeManager.removeDatanode due to DatanodeManager found a lost heartbeat
datanode, the block may still stored on that datanode's disk safely. So after
resolve the temporary issue (power, network...) and start the datanode process
again, we will have missing block back.
> 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)
