[
https://issues.apache.org/jira/browse/HADOOP-18324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17686370#comment-17686370
]
ASF GitHub Bot commented on HADOOP-18324:
-----------------------------------------
steveloughran commented on PR #5369:
URL: https://github.com/apache/hadoop/pull/5369#issuecomment-1424005574
don't know what went wrong with the build; EOF during the npm build
```
[INFO]
------------------------------------------------------------------------
[ERROR] Failed to execute goal
com.github.eirslett:frontend-maven-plugin:1.11.2:install-node-and-yarn (install
node and yarn) on project hadoop-yarn-applications-catalog-webapp: Could not
extract the Node archive: Could not extract archive:
'/home/jenkins/jenkins-home/workspace/hadoop-multibranch_PR-5369/yetus-m2/hadoop-branch-3.3.5-patch-0/com/github/eirslett/node/12.22.1/node-12.22.1-linux-x64.tar.gz':
EOFException -> [Help 1]
[ERROR]
```
This PR is a quick revert only of the IPC stuff. This is one of the two
blockers for 3.3.5 and IMO it's dangerous to try and rush through a fix for
this with time pressure. yes, the thread leakage issue will remain, but at
least we know the shutdown works -and as that is a common activity, I'd prefer
that to be working.
If people with private forks who have the original patch can help work on
the ultimate fix, we can get it into the followup release
> 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
> Fix For: 3.4.0, 3.3.5, 2.10.3
>
> Time Spent: 2h 50m
> 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]
