Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Mon, 29 Aug 2011 06:08:38 +0000 (UTC)
From: "Uma Maheswara Rao G (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: 
 <199387290.2292.1314598118198.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=13092653#comment-13092653 ] 

Uma Maheswara Rao G commented on HDFS-1779:
-------------------------------------------

Thanks a lot to Todd and Hairong for review!
 
{quote}
since that puts it into the blockmap but not the "targets" array. Wouldn't it be more correct to put it into the INodeFileUnderConstruction's targets array?
{quote}
 Good point. I will take a look.
 I will update the patch as per your comments. or Hairong, do you have patch ready?

Thanks,
Uma

> 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