[
https://issues.apache.org/jira/browse/HADOOP-18324?focusedWorklogId=790624&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-790624
]
ASF GitHub Bot logged work on HADOOP-18324:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 13/Jul/22 22:52
Start Date: 13/Jul/22 22:52
Worklog Time Spent: 10m
Work Description: mccormickt12 commented on code in PR #4527:
URL: https://github.com/apache/hadoop/pull/4527#discussion_r920572884
##########
hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/ipc/Client.java:
##########
@@ -1183,51 +1158,7 @@ public void sendRpcRequest(final Call call)
final ResponseBuffer buf = new ResponseBuffer();
header.writeDelimitedTo(buf);
RpcWritable.wrap(call.rpcRequest).writeTo(buf);
-
- synchronized (sendRpcRequestLock) {
- Future<?> senderFuture = sendParamsExecutor.submit(new Runnable() {
Review Comment:
please update the comment above, as `sendParamsExecutor` no longer exists
Issue Time Tracking
-------------------
Worklog Id: (was: 790624)
Time Spent: 2h 10m (was: 2h)
> 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: 2h 10m
> 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]
