[
https://issues.apache.org/jira/browse/HDFS-10433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15305138#comment-15305138
]
Hadoop QA commented on HDFS-10433:
----------------------------------
| (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 5s {color}
| {color:red} HDFS-10433 does not apply to trunk. Rebase required? Wrong
Branch? See https://wiki.apache.org/hadoop/HowToContribute for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12806785/h10433_20160527.patch
|
| JIRA Issue | HDFS-10433 |
| Console output |
https://builds.apache.org/job/PreCommit-HDFS-Build/15597/console |
| Powered by | Apache Yetus 0.2.0 http://yetus.apache.org |
This message was automatically generated.
> Make retry also works well for Async DFS
> ----------------------------------------
>
> Key: HDFS-10433
> URL: https://issues.apache.org/jira/browse/HDFS-10433
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: hdfs
> Reporter: Xiaobing Zhou
> Assignee: Tsz Wo Nicholas Sze
> Attachments: h10433_20160524.patch, h10433_20160525.patch,
> h10433_20160525b.patch, h10433_20160527.patch
>
>
> In current Async DFS implementation, file system calls are invoked and
> returns Future<?> immediately to clients. Clients call Future#get to retrieve
> final results. Future#get internally invokes a chain of callbacks residing in
> ClientNamenodeProtocolTranslatorPB, ProtobufRpcEngine and ipc.Client. The
> callback path bypasses the original retry layer/logic designed for
> synchronous DFS. This proposes refactoring to make retry also works for Async
> DFS.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
