[
https://issues.apache.org/jira/browse/YARN-8404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16504271#comment-16504271
]
Rohith Sharma K S commented on YARN-8404:
-----------------------------------------
Making TimelineServiceV1Publisher#appFinished synchronous is very dangerous. If
ATS1/1.5 daemon is down then primary AsyncDispatcher thread is blocked which
makes primary dispatcher event queue grow up.
> RM Recovery is delayed much if ATS1/1.5 server is not running.
> ---------------------------------------------------------------
>
> Key: YARN-8404
> URL: https://issues.apache.org/jira/browse/YARN-8404
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Rohith Sharma K S
> Assignee: Rohith Sharma K S
> Priority: Critical
>
> 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: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
