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 "Amithsha (Jira)" <ji...@apache.org> on 2020/08/17 17:10:00 UTC
[jira] [Commented] (YARN-10368) Log aggregation reset to NOT_START
after RM restart.
[ https://issues.apache.org/jira/browse/YARN-10368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17179134#comment-17179134 ]
Amithsha commented on YARN-10368:
---------------------------------
+1
> Log aggregation reset to NOT_START after RM restart.
> ----------------------------------------------------
>
> Key: YARN-10368
> URL: https://issues.apache.org/jira/browse/YARN-10368
> Project: Hadoop YARN
> Issue Type: Bug
> Components: nodemanager, resourcemanager, yarn
> Affects Versions: 3.2.1
> Reporter: Anuj
> Priority: Major
> Attachments: Screenshot 2020-07-27 at 2.35.15 PM.png
>
>
> Attempt recovered after RM restart the log aggregation status is not preserved and it come to NOT_START.
> From NOT_START it never moves to TIMED_OUT and then never cleaned up RM App in memory resulting max-completed-app in memory limit hit and RM stops accepting new apps.
> https://issues.apache.org/jira/browse/YARN-7952
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org