[
https://issues.apache.org/jira/browse/YARN-8404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16510949#comment-16510949
]
Hudson commented on YARN-8404:
------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #14419 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/14419/])
YARN-8404. Timeline event publish need to be async to avoid Dispatcher (sunilg:
rev 6307962b932e0ee69ba61f5796388c175d79195a)
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/metrics/TimelineServiceV1Publisher.java
> Timeline event publish need to be async to avoid Dispatcher thread leak in
> case ATS is down
> -------------------------------------------------------------------------------------------
>
> Key: YARN-8404
> URL: https://issues.apache.org/jira/browse/YARN-8404
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 3.1.0, 3.0.2
> Reporter: Rohith Sharma K S
> Assignee: Rohith Sharma K S
> Priority: Blocker
> Fix For: 2.10.0, 3.2.0, 3.1.1, 3.0.4
>
> Attachments: YARN-8404.01.patch
>
>
> It is observed that if ATS1/1.5 daemon is not running, RM recovery is delayed
> as long as timeline client get timed out for each applications. By default,
> timed out will take around 5 mins. If completed applications are more then
> amount of time RM will wait is *(number of completed applications in a
> cluster * 5 minutes)* which is kind of hanged.
> Primary reason for this behavior is YARN-3044 YARN-4129 which refactor
> existing system metric publisher. This refactoring made appFinished event as
> synchronous which was asynchronous earlier.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
