[
https://issues.apache.org/jira/browse/HDFS-10433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15306045#comment-15306045
]
Tsz Wo Nicholas Sze commented on HDFS-10433:
--------------------------------------------
Jenkins somehow tested h10433_20160528b.patch again but not
/h10433_20160528c.patch.
> 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, 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: [email protected]
For additional commands, e-mail: [email protected]
