Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Mon, 29 Oct 2012 19:00:13 +0000 (UTC)
From: "Robert Joseph Evans (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <452714780.40275.1351537213403.JavaMail.jiratomcat@arcas>
In-Reply-To: <757108863.33796.1351289112614.JavaMail.jiratomcat@arcas>
Subject: [jira] [Updated] (HADOOP-8986) Server$Call object is never released
 after it is sent
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Robert Joseph Evans updated HADOOP-8986:
----------------------------------------

    Status: Patch Available  (was: Open)
    
> Server$Call object is never released after it is sent
> -----------------------------------------------------
>
>                 Key: HADOOP-8986
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8986
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: ipc
>    Affects Versions: 0.23.4, 2.0.2-alpha
>            Reporter: Robert Joseph Evans
>            Assignee: Robert Joseph Evans
>            Priority: Critical
>         Attachments: HADOOP-8986.txt
>
>
> When an IPC response cannot be returned without blocking an Server$Call object is attached to the SelectionKey of the write selector.  However the call object is never removed from the SlectionKey. So for a connection that rarely has large responses but is long lived there is a lot of data.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira