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

Zesheng Wu updated HDFS-4916:
-----------------------------

          Description: When a new datanode is added to the pipeline, the client 
will trigger the block transfer process. In the current implementation, the src 
datanode calls the run() method of the DataTransfer to transfer the block, this 
method will mask the IOExceptions during the transfering, and will make the 
client not realize the failure during the transferring, as a result the client 
will mistake the failing transferring as successful one.   (was: When a new 
datanode is added to the pipeline, the client will trigger the block transfer 
process. In the current implementation, the src datanode calls the run() method 
of the DataTransfer to transfer the block, this method will mask the 
IOExceptions during the transfering, and will make the client not realize the 
failure during the transfering.)
    Affects Version/s: 2.0.5-alpha
    
> DataTransfer may mask the IOException during block transfering
> --------------------------------------------------------------
>
>                 Key: HDFS-4916
>                 URL: https://issues.apache.org/jira/browse/HDFS-4916
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: datanode
>    Affects Versions: 2.0.4-alpha, 2.0.5-alpha
>            Reporter: Zesheng Wu
>            Priority: Blocker
>         Attachments: 4916.v0.patch
>
>
> When a new datanode is added to the pipeline, the client will trigger the 
> block transfer process. In the current implementation, the src datanode calls 
> the run() method of the DataTransfer to transfer the block, this method will 
> mask the IOExceptions during the transfering, and will make the client not 
> realize the failure during the transferring, as a result the client will 
> mistake the failing transferring as successful one. 

--
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

Reply via email to