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 "Aihua Xu (Jira)" <ji...@apache.org> on 2022/04/17 22:34:00 UTC

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

     [ https://issues.apache.org/jira/browse/HADOOP-13144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aihua Xu updated HADOOP-13144:
------------------------------
    Attachment: HADOOP-13144_overload_enhancement.patch

> 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-performance.patch, HADOOP-13144.000.patch, HADOOP-13144.001.patch, HADOOP-13144.002.patch, HADOOP-13144.003.patch, HADOOP-13144_overload_enhancement.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.20.1#820001)

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