Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Wed, 10 Aug 2011 19:38:27 +0000 (UTC)
From: "Hadoop QA (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: 
 <954569462.25018.1313005107336.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1754194135.6119.1300891445821.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HDFS-1779) After NameNode restart , Clients can
 not read partial files even after client invokes Sync.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Hadoop QA commented on HDFS-1779:
---------------------------------

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12489473/HDFS-1779.1.patch
  against trunk revision 1155998.

    +1 @author.  The patch does not contain any @author tags.

    +1 tests included.  The patch appears to include 7 new or modified tests.

    -1 patch.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/1070//console

This message is automatically generated.

> After NameNode restart , Clients can not read partial files even after client invokes Sync.
> -------------------------------------------------------------------------------------------
>
>                 Key: HDFS-1779
>                 URL: https://issues.apache.org/jira/browse/HDFS-1779
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: data-node, name-node
>    Affects Versions: 0.20-append
>         Environment: Linux
>            Reporter: Uma Maheswara Rao G
>            Assignee: Uma Maheswara Rao G
>             Fix For: 0.20-append
>
>         Attachments: HDFS-1779.1.patch, HDFS-1779.patch
>
>
> In Append HDFS-200 issue,
> If file has 10 blocks and after writing 5 blocks if client invokes sync method then NN will persist the blocks information in edits. 
> After this if we restart the NN, All the DataNodes will reregister with NN. But DataNodes are not sending the blocks being written information to NN. DNs are sending the blocksBeingWritten information in DN startup. So, here NameNode can not find that the 5 persisted blocks belongs to which datanodes. This information can build based on block reports from DN. Otherwise we will loose this 5 blocks information even NN persisted that block information in edits. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira