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] [Commented] (HADOOP-10300) Allowed deferred sending of call responses
Date Tue, 09 Sep 2014 17:30:29 GMT

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

Daryn Sharp commented on HADOOP-10300:
--------------------------------------

Could I get a review so I can put up a patch for decoupling the wait for edit logging syncing
from the ipc handler's lifecycle?

> 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.3.4#6332)

Mime
View raw message