[ https://issues.apache.org/jira/browse/YARN-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16105168#comment-16105168 ] Naganarasimha G R commented on YARN-65: --------------------------------------- Thanks for working on it [~manirajv06@gmail.com] based on the discussion we had offline. Have assigned the issue to you. I see few main issues in the patch. # RMAppImpl, ln no 1090, RMAppRecoveredTransition you are setting many of the parameters to null! what if the app is running ? # RMAppImpl, ln no 1144, AddApplicationToSchedulerTransition, on add application all are getting set to null ! # RMAppImpl, ln no 2029, setApplicationACLs should not be set to null, as it will be required to validate while showing apps > 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: Manikandan R > Attachments: YARN-65.001.patch > > > 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.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: yarn-issues-help@hadoop.apache.org