[ https://issues.apache.org/jira/browse/HDFS-9959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15194482#comment-15194482 ]
yunjiong zhao commented on HDFS-9959: ------------------------------------- It shouldn't, it will only print those blocks which was removed from last live datanode and do belong to a file. In real production cluster, this should not happen often, otherwise there will be lots of corrupt files. > 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)