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

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

Hi Nicolas,

Thanks a lot for digging into DFS changes.

 By seeing the description, HDFS-3222 can fix partly, and there are other 
changes to read the block from all DNs and check specific to 
ReplicaNotFoundException. If it sees ReplicaNotFoundException from all DNs, 
then only we will return 0, otherwise we will throw exception.
Combining these changes should fix this problems. But I don't think we have the 
specific exception like ReplicaNotFoundException in branch-1.
I think this new category of exceptions got introduced as part new Appned 
design. So, distinquishing the replica not found exception and other remote 
exceptions will be difficult in branch-1 ( let me check the latest code, 
whether it is possible due to many issues backporting recently)


Thanks
Uma
                
> 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
>            Priority: Critical
>
> 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: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to