You are viewing a plain text version of this content. The canonical link for it is here.

Posted to hdfs-dev@hadoop.apache.org by "Konstantin Shvachko (JIRA)" <ji...@apache.org> on 2015/03/13 20:14:38 UTC

[jira] [Created] (HDFS-7930) commitBlockSynchronization() does not remove locations, which were not confirmed

Konstantin Shvachko created HDFS-7930:
-----------------------------------------

             Summary: 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)