[
https://issues.apache.org/jira/browse/HADOOP-18324?focusedWorklogId=787320&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-787320
]
ASF GitHub Bot logged work on HADOOP-18324:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 02/Jul/22 10:38
Start Date: 02/Jul/22 10:38
Worklog Time Spent: 10m
Work Description: ZanderXu commented on PR #4527:
URL: https://github.com/apache/hadoop/pull/4527#issuecomment-1172876882
@omalley I'm very happy that you noticing this issue and working on it. This
problem occurs frequently in out prod environment when the network is abnormal.
About this rpc sending model, I have one question and looking forward your
feedback.
- What's the underlying idea for using asynchronous threads to send request
synchronously?
In addition to guaranteeing that only one request is sent at the same time,
does it need to guarantee the order of sending?
If it is just to ensure mutual exclusive transmission, can we do it by a
sync lock? And if so, we can use the business thread to send it's own request
directly. And we can remove the send thread in `Client.java`.
Issue Time Tracking
-------------------
Worklog Id: (was: 787320)
Time Spent: 0.5h (was: 20m)
> 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: 0.5h
> 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]
