You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Rohith Sharma K S (JIRA)" <ji...@apache.org> on 2018/06/07 05:39:00 UTC
[jira] [Moved] (YARN-8404) RM Recovery is delayed much if ATS1/1.5
server is not running.
[ https://issues.apache.org/jira/browse/YARN-8404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rohith Sharma K S moved MAPREDUCE-7106 to YARN-8404:
----------------------------------------------------
Key: YARN-8404 (was: MAPREDUCE-7106)
Project: Hadoop YARN (was: Hadoop Map/Reduce)
> 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-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org