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 "Jason Kace (JIRA)" <ji...@apache.org> on 2016/05/13 22:31:12 UTC

[jira] [Created] (HADOOP-13144) Enhancing IPC client throughput via multiple connections per user

Jason Kace created HADOOP-13144:
-----------------------------------

             Summary: 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
            Priority: Minor
             Fix For: 2.8.0


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
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org