Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Fri, 20 Mar 2015 21:15:39 +0000 (UTC)
From: "Daryn Sharp (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.12691708.1390937369000.162299.1426886139476@Atlassian.JIRA>
In-Reply-To: <JIRA.12691708.1390937369000@Atlassian.JIRA>
References: <JIRA.12691708.1390937369000@Atlassian.JIRA>
 <JIRA.12691708.1390937369576@arcas>
Subject: [jira] [Updated] (HADOOP-10300) Allowed deferred sending of call
 responses
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ 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

Updated patch.

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