hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sangjin Lee (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-7930) commitBlockSynchronization() does not remove locations
Date Mon, 27 Jul 2015 14:57:05 GMT

    [ https://issues.apache.org/jira/browse/HDFS-7930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14642820#comment-14642820
] 

Sangjin Lee commented on HDFS-7930:
-----------------------------------

The backport to 2.6.0 is more or less straightforward but for the following:

- the test changes were made in TestFileTruncate which does not exist in 2.6, so it does not
apply
- changed the method argument type from BlockInfoContiguous (only in 2.7) to BlockInfo
- modified the logging statement (the upstream code is for slf4j Logger which is new in 2.7)

I'm going to attach a suggested patch for 2.6.0.

> 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
>              Labels: 2.6.1-candidate
>             Fix For: 2.7.0
>
>         Attachments: HDFS-7930.001.patch, HDFS-7930.002.patch, HDFS-7930.003.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)

Mime
View raw message