[
https://issues.apache.org/jira/browse/HDFS-4916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16914042#comment-16914042
]
Hadoop QA commented on HDFS-4916:
---------------------------------
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 7s{color}
| {color:red} HDFS-4916 does not apply to trunk. Rebase required? Wrong Branch?
See https://wiki.apache.org/hadoop/HowToContribute for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HDFS-4916 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12588510/4916.v0.patch |
| Console output |
https://builds.apache.org/job/PreCommit-HDFS-Build/27647/console |
| Powered by | Apache Yetus 0.8.0 http://yetus.apache.org |
This message was automatically generated.
> 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
> Assignee: Lisheng Sun
> Priority: Critical
> Labels: BB2015-05-TBR
> 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 was sent by Atlassian Jira
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
