Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Sat, 29 Sep 2012 08:04:08 +1100 (NCT)
From: "Matt Foley (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <838264017.140913.1348866248091.JavaMail.jiratomcat@arcas>
In-Reply-To: <1005358690.90507.1343040694858.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Commented] (HDFS-3701) HDFS may miss the final block when
 reading a file opened for writing if one of the datanode is dead
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Matt Foley commented on HDFS-3701:
----------------------------------

merged to branch-1.1
                
> HDFS may miss the final block when reading a file opened for writing if one of the datanode is dead
> ---------------------------------------------------------------------------------------------------
>
>                 Key: HDFS-3701
>                 URL: https://issues.apache.org/jira/browse/HDFS-3701
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: hdfs client
>    Affects Versions: 1.0.3
>            Reporter: nkeywal
>            Assignee: nkeywal
>            Priority: Critical
>             Fix For: 1.1.0
>
>         Attachments: HDFS-3701.branch-1.v2.merged.patch, HDFS-3701.branch-1.v3.patch, HDFS-3701.branch-1.v4.patch, HDFS-3701.ontopof.v1.patch, HDFS-3701.patch
>
>
> When the file is opened for writing, the DFSClient calls one of the datanode owning the last block to get its size. If this datanode is dead, the socket exception is shallowed and the size of this last block is equals to zero. This seems to be fixed on trunk, but I didn't find a related Jira. On 1.0.3, it's not fixed. It's on the same area as HDFS-1950 or HDFS-3222.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira