[
https://issues.apache.org/jira/browse/HADOOP-6713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12858392#action_12858392
]
dhruba borthakur commented on HADOOP-6713:
------------------------------------------
Hi Christian, I agree with you. We have around 40K clients hitting the namenode
and the NN ( inspite of running NN on a newest and greatest Nehalem) has one
CPU completely maxed out by the Server.Listener thread.
> 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.
