[ https://issues.apache.org/jira/browse/HADOOP-13144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16419230#comment-16419230 ]
Daryn Sharp commented on HADOOP-13144: -------------------------------------- I'm uneasy with the entire premise of this jira. This feature better not be used in the general use case. Regardless, this has no impact on the ConnectionId cache, not that I would want it to. How do you intend to use it? Exposing and directly utilizing the what-should-be-private bowels of the IPC code is going to make future development very hard. > 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.000.patch, HADOOP-13144.001.patch, > HADOOP-13144.002.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 (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org