You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Suresh Srinivas (JIRA)" <ji...@apache.org> on 2010/07/02 23:51:55 UTC
[jira] Commented: (HADOOP-6713) The RPC server Listener thread is a
scalability bottleneck
[ https://issues.apache.org/jira/browse/HADOOP-6713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12884817#action_12884817 ]
Suresh Srinivas commented on HADOOP-6713:
-----------------------------------------
Comments for Y20 version of the patch.
# Please remove YAHOO-CHANGES.txt from the patch
# Remove blank changes that is diff between two patches: lines 51, 73, 138, 171, 203, 220. There could be others.
# line 283 exceeds 80 chars
> 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.21.0
> Reporter: dhruba borthakur
> Assignee: Dmytro Molkov
> Fix For: 0.21.0
>
> Attachments: HADOOP-6713-rel20.patch, HADOOP-6713.2.patch, HADOOP-6713.patch
>
>
> 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.