[ https://issues.apache.org/jira/browse/HDFS-7930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14365845#comment-14365845 ]
Konstantin Shvachko commented on HDFS-7930: ------------------------------------------- Actually taking the last observation back. You need to call {{setDataNodeDead()}} after {{shutdown()}}, otherwise NN can schedule recovery (with 1/3 probablity) on the dead DN as a primary. It will wait for the heartbeat from it, but will never receive it because it is down. > commitBlockSynchronization() does not remove locations > ------------------------------------------------------ > > Key: HDFS-7930 > URL: https://issues.apache.org/jira/browse/HDFS-7930 > Project: Hadoop HDFS > Issue Type: Bug > Components: namenode > Affects Versions: 2.7.0 > Reporter: Konstantin Shvachko > Assignee: Yi Liu > Priority: Blocker > Attachments: HDFS-7930.001.patch, HDFS-7930.002.patch > > > When {{commitBlockSynchronization()}} has less {{newTargets}} than in the > original block it does not remove unconfirmed locations. This results in that > the the block stores locations of different lengths or genStamp (corrupt). -- This message was sent by Atlassian JIRA (v6.3.4#6332)