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 "Tsz Wo Nicholas Sze (JIRA)" <ji...@apache.org> on 2016/06/01 00:20:12 UTC
[jira] [Updated] (HADOOP-13226) Support async call retry and
failover
[ https://issues.apache.org/jira/browse/HADOOP-13226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tsz Wo Nicholas Sze updated HADOOP-13226:
-----------------------------------------
Resolution: Fixed
Fix Version/s: 2.8.0
Status: Resolved (was: Patch Available)
Thanks Jing for reviewing the patches and the great ideas!
I have committed this.
> 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
> Fix For: 2.8.0
>
> 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