[
https://issues.apache.org/jira/browse/HADOOP-12909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15205710#comment-15205710
]
Haohui Mai commented on HADOOP-12909:
-------------------------------------
I'm concerned about the complexity and the effort to support it down the road.
I understand in short term this is something that can be patched. However, we
have enough troubles in today's IPC, maintaining it is definitely a challenging
task especially. Does it make more sense to invest in other existing solutions
that are more well tested, such as gRPC, which will allow us to make more
effective investments in other areas?
> Change ipc.Client to support asynchronous calls
> -----------------------------------------------
>
> Key: HADOOP-12909
> URL: https://issues.apache.org/jira/browse/HADOOP-12909
> Project: Hadoop Common
> Issue Type: New Feature
> Components: ipc
> Reporter: Tsz Wo Nicholas Sze
> Assignee: Xiaobing Zhou
> Attachments: HADOOP-12909-HDFS-9924.000.patch,
> HADOOP-12909-HDFS-9924.001.patch, HADOOP-12909-HDFS-9924.002.patch,
> HADOOP-12909-HDFS-9924.003.patch
>
>
> In ipc.Client, the underlying mechanism is already supporting asynchronous
> calls -- the calls shares a connection, the call requests are sent using a
> thread pool and the responses can be out of order. Indeed, synchronous call
> is implemented by invoking wait() in the caller thread in order to wait for
> the server response.
> In this JIRA, we change ipc.Client to support asynchronous mode. In
> asynchronous mode, it return once the request has been sent out but not wait
> for the response from the server.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
