[
https://issues.apache.org/jira/browse/HADOOP-13144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16995816#comment-16995816
]
Íñigo Goiri commented on HADOOP-13144:
--------------------------------------
Thanks [~Symious] for the update.
Now that we have proof that this is actually helpful, we should just do the RPC
change and then do the Router changes in HDFS-13274.
The only part I'm not sure about which interfaces in RpcEngine and RPC we
should extend.
Maybe just stick with the ones here.
The other question is what to do with 3.3 and 2.10.
> Enhancing IPC client throughput via multiple connections per user
> -----------------------------------------------------------------
>
> Key: HADOOP-13144
> URL: https://issues.apache.org/jira/browse/HADOOP-13144
> Project: Hadoop Common
> Issue Type: Improvement
> Components: ipc
> Reporter: Jason Kace
> Assignee: Íñigo Goiri
> Priority: Minor
> Attachments: HADOOP-13144-branch-2.9.001.patch,
> HADOOP-13144-branch-2.9.002.patch, HADOOP-13144-branch-2.9.003.patch,
> HADOOP-13144-branch-2.9.004.patch, HADOOP-13144-performance.patch,
> HADOOP-13144.000.patch, HADOOP-13144.001.patch, HADOOP-13144.002.patch,
> HADOOP-13144.003.patch
>
>
> The generic IPC client ({{org.apache.hadoop.ipc.Client}}) utilizes a single
> connection thread for each {{ConnectionId}}. The {{ConnectionId}} is unique
> to the connection's remote address, ticket and protocol. Each ConnectionId
> is 1:1 mapped to a connection thread by the client via a map cache.
> The result is to serialize all IPC read/write activity through a single
> thread for a each user/ticket + address. If a single user makes repeated
> calls (1k-100k/sec) to the same destination, the IPC client becomes a
> bottleneck.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
