Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-dev@hadoop.apache.org
Date: Wed, 29 Jan 2014 20:12:47 +0000 (UTC)
From: "Jason Lowe (JIRA)" <jira@apache.org>
To: common-dev@hadoop.apache.org
Message-ID: <JIRA.12688877.1389740291628.5053.1391026367674@arcas>
In-Reply-To: <JIRA.12688877.1389740291628@arcas>
References: <JIRA.12688877.1389740291628@arcas>
Subject: [jira] [Resolved] (HADOOP-10233) RPC lacks output flow control
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jason Lowe resolved HADOOP-10233.
---------------------------------

    Resolution: Duplicate

> RPC lacks output flow control
> -----------------------------
>
>                 Key: HADOOP-10233
>                 URL: https://issues.apache.org/jira/browse/HADOOP-10233
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: ipc
>    Affects Versions: 2.0.0-alpha, 3.0.0
>            Reporter: Daryn Sharp
>            Priority: Critical
>
> The RPC layer has input flow control via the callq, however it lacks any output flow control.  A handler will try to directly send the response.  If the full response is not sent then it is queued for the background responder thread.  The RPC layer may end up queuing so many buffers that it "locks" up in GC.


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