[
https://issues.apache.org/jira/browse/HADOOP-18324?focusedWorklogId=787363&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-787363
]
ASF GitHub Bot logged work on HADOOP-18324:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 03/Jul/22 00:39
Start Date: 03/Jul/22 00:39
Worklog Time Spent: 10m
Work Description: omalley commented on PR #4527:
URL: https://github.com/apache/hadoop/pull/4527#issuecomment-1172985170
The extra thread is used so that if the calling thread is interrupted while
the request is being written to the socket, that the write is not interrupted.
Basically, it is ensuring that the socket doesn't have partial requests sent to
it.
Without that, Hadoop would need to resynchronize by closing the socket.
Issue Time Tracking
-------------------
Worklog Id: (was: 787363)
Time Spent: 40m (was: 0.5h)
> Interrupting RPC Client calls can lead to thread exhaustion
> -----------------------------------------------------------
>
> Key: HADOOP-18324
> URL: https://issues.apache.org/jira/browse/HADOOP-18324
> Project: Hadoop Common
> Issue Type: Bug
> Components: ipc
> Affects Versions: 3.4.0, 2.10.2, 3.3.3
> Reporter: Owen O'Malley
> Assignee: Owen O'Malley
> Priority: Critical
> Labels: pull-request-available
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Currently the IPC client creates a boundless number of threads to write the
> rpc request to the socket. The NameNode uses timeouts on its RPC calls to the
> Journal Node and a stuck JN will cause the NN to create an infinite set of
> threads.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
