Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Message-ID: <28549148.5131271657510999.JavaMail.jira@thor>
Date: Mon, 19 Apr 2010 02:11:50 -0400 (EDT)
From: "Christian Kunz (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-6713) The RPC server Listener thread is a
 scalability bottleneck
In-Reply-To: <20387500.4981271656489920.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Christian Kunz commented on HADOOP-6713:
----------------------------------------

That would be a great improvement for our clusters as well. Probably for any cluster with a lot of clients not necessarily being map-reduce applications.

> The RPC server Listener thread is a scalability bottleneck
> ----------------------------------------------------------
>
>                 Key: HADOOP-6713
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6713
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: ipc
>    Affects Versions: 0.20.0, 0.20.1, 0.20.2
>            Reporter: dhruba borthakur
>            Assignee: Dmytro Molkov
>
> The Hadoop RPC Server implementation has a single Listener thread that reads data from the socket and puts them into a call queue. This means that this single thread can pull RPC requests off the network only as fast as a single CPU can execute. This is a scalability bottlneck in our cluster.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.