You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2016/05/31 23:39:13 UTC

[jira] [Commented] (HADOOP-13226) Support async call retry and failover

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

Hadoop QA commented on HADOOP-13226:
------------------------------------

| (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} HADOOP-13226 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/12806846/h10433_20160528c.patch |
| JIRA Issue | HADOOP-13226 |
| Console output | https://builds.apache.org/job/PreCommit-HADOOP-Build/9632/console |
| Powered by | Apache Yetus 0.4.0-SNAPSHOT   http://yetus.apache.org |


This message was automatically generated.



> Support async call retry and failover
> -------------------------------------
>
>                 Key: HADOOP-13226
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13226
>             Project: Hadoop Common
>          Issue Type: New Feature
>          Components: io, ipc
>            Reporter: Xiaobing Zhou
>            Assignee: Tsz Wo Nicholas Sze
>         Attachments: h10433_20160524.patch, h10433_20160525.patch, h10433_20160525b.patch, h10433_20160527.patch, h10433_20160528.patch, h10433_20160528c.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: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org