[
https://issues.apache.org/jira/browse/HADOOP-13144?focusedWorklogId=789244&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-789244
]
ASF GitHub Bot logged work on HADOOP-13144:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 09/Jul/22 12:44
Start Date: 09/Jul/22 12:44
Worklog Time Spent: 10m
Work Description: ZanderXu opened a new pull request, #4542:
URL: https://github.com/apache/hadoop/pull/4542
### Description of PR
Jira ID: [HADOOP-13144](https://issues.apache.org/jira/browse/HADOOP-13144)
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.
Issue Time Tracking
-------------------
Worklog Id: (was: 789244)
Remaining Estimate: 0h
Time Spent: 10m
> 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
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
