hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daryn Sharp (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-10300) Allowed deferred sending of call responses
Date Thu, 14 Aug 2014 18:26:13 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-10300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Daryn Sharp updated HADOOP-10300:
---------------------------------

    Attachment: HADOOP-10300.patch

Add a ref count for sending of responses.  This will enable a proxy method in the handler
to mark the call for a postponed response, but allow the ipc layer to fully prepare and encode
the response.  The sendResponse becomes a no-op.  The caller that postponed the response is
responsible for ensuring that  sendResponse is again invoked to actually send the response.

> 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
>         Attachments: HADOOP-10300.patch
>
>
> 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.2#6252)

Mime
View raw message