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 "Denis Bolshakov (JIRA)" <ji...@apache.org> on 2016/10/31 16:25:59 UTC

[jira] [Commented] (YARN-65) Reduce RM app memory footprint once app has completed

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

Denis Bolshakov commented on YARN-65:
-------------------------------------

[~vinodkv], I suggest to close this ticket:
1. yarn.resource.max-completed-applications has been renamed, and current default is 1000
2. RMAppManager keeps a list of ApplicationId (completedApps), not list of RMAppImpl, so it does not have such overhead anymore.

> Reduce RM app memory footprint once app has completed
> -----------------------------------------------------
>
>                 Key: YARN-65
>                 URL: https://issues.apache.org/jira/browse/YARN-65
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: resourcemanager
>    Affects Versions: 0.23.3
>            Reporter: Jason Lowe
>
> The ResourceManager holds onto a configurable number of completed applications (yarn.resource.max-completed-applications, defaults to 10000), and the memory footprint of these completed applications can be significant.  For example, the {{submissionContext}} in RMAppImpl contains references to protocolbuffer objects and other items that probably aren't necessary to keep around once the application has completed.  We could significantly reduce the memory footprint of the RM by releasing objects that are no longer necessary once an application completes.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org