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 "Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org> on 2015/11/03 18:28:27 UTC

[jira] [Commented] (YARN-4325) purge app state from NM state-store should be independent of log aggregation

    [ https://issues.apache.org/jira/browse/YARN-4325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14987678#comment-14987678 ] 

Vinod Kumar Vavilapalli commented on YARN-4325:
-----------------------------------------------

[~djp], the JIRA is a little light on details, will help if you can paste exception / log messages etc.

Also, does this only happen with mis-configuration? And you are planning to work on this soon? If not, I'd not hold 2.7.2 off for this.

> purge app state from NM state-store should be independent of log aggregation
> ----------------------------------------------------------------------------
>
>                 Key: YARN-4325
>                 URL: https://issues.apache.org/jira/browse/YARN-4325
>             Project: Hadoop YARN
>          Issue Type: Bug
>    Affects Versions: 2.6.0
>            Reporter: Junping Du
>            Assignee: Junping Du
>            Priority: Critical
>
> From a long running cluster, we found tens of thousands of stale apps still be recovered in NM restart recovery. The reason is some wrong configuration setting to log aggregation so the end of log aggregation events are not received so stale apps are not purged properly. We should make sure the removal of app state to be independent of log aggregation life cycle. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)