[
https://issues.apache.org/jira/browse/YARN-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15983262#comment-15983262
]
Naganarasimha G R commented on YARN-65:
---------------------------------------
[~jlowe], wow never expected to hit a issue which is so old.
But was just thinking about a simpler solution where to set the references of
the unused fields to null in the RMAppImpl instance. As you mentioned (long
before) we were seeing many of the fields used in ApplicationSubmissionContext/
AM's ContainerLaunchContext are not required for reporting purpose hence
planning to set them to null on the completion of the app and also at the same
time we need to handle the same during recovery too. Thoughts ?
> 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
> Assignee: Naganarasimha G R
>
> 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.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
