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 "Siddharth Seth (JIRA)" <ji...@apache.org> on 2016/03/11 00:33:40 UTC

[jira] [Commented] (HADOOP-12909) Change ipc.Client to support asynchronous calls

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

Siddharth Seth commented on HADOOP-12909:
-----------------------------------------

There are potential problems with supporting client side calls without fixing the server side - the main one being that all handler threads on the server can end up getting blocked. Of course, the same would happen if the client app were to create it's own threads and make remote calls (FileSystem for instance).
The future based approach mentioned here and other related jiras ends up simplifying client code; however frameworks need to be aware of the potential affect on the server.

> 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
>
> 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)