hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uma Maheswara Rao G (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-1779) After NameNode restart , Clients can not read partial files even after client invokes Sync.
Date Fri, 05 Aug 2011 13:22:31 GMT

     [ https://issues.apache.org/jira/browse/HDFS-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Uma Maheswara Rao G updated HDFS-1779:
--------------------------------------

    Attachment: HDFS-1779.1.patch

> 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

        

Mime
View raw message