[
https://issues.apache.org/jira/browse/HDFS-7930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14361304#comment-14361304
]
Byron Wong commented on HDFS-7930:
----------------------------------
The failure is reproducible (after applying the latest patch from HDFS-7886) by
commenting out the {{cluster.triggerBlockReports();}} in
{{testTruncateWithDataNodesRestartImmediately}} and running all test in
TestFileTruncate.
> commitBlockSynchronization() does not remove locations, which were not
> confirmed
> --------------------------------------------------------------------------------
>
> 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
> Priority: Blocker
>
> 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)
