hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Byron Wong (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-7930) commitBlockSynchronization() does not remove locations, which were not confirmed
Date Fri, 13 Mar 2015 23:25:38 GMT

    [ 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)

Mime
View raw message