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 "Suresh Srinivas (JIRA)" <ji...@apache.org> on 2014/01/28 20:58:39 UTC

[jira] [Commented] (HADOOP-10300) Allowed deferred sending of call responses

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

Suresh Srinivas commented on HADOOP-10300:
------------------------------------------

Big +1 for this feature. This will be able to reduce the number of handlers we currently need. Only thing that we need to protect is accepting too many requests and responding to it becomes a bottleneck. That can be addressed as we continue to work on this issue.

> Allowed deferred sending of call responses
> ------------------------------------------
>
>                 Key: HADOOP-10300
>                 URL: https://issues.apache.org/jira/browse/HADOOP-10300
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: ipc
>    Affects Versions: 2.0.0-alpha, 3.0.0
>            Reporter: Daryn Sharp
>            Assignee: Daryn Sharp
>
> RPC handlers currently do not return until the RPC call completes and response is sent, or a partially sent response has been queued for the responder.  It would be useful for a proxy method to notify the handler to not yet the send the call's response.
> An potential use case is a namespace handler in the NN might want to return before the edit log is synced so it can service more requests and allow increased batching of edits per sync.  Background syncing could later trigger the sending of the call response to the client.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)