[
https://issues.apache.org/jira/browse/MAPREDUCE-2649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072353#comment-13072353
]
Thomas Graves commented on MAPREDUCE-2649:
------------------------------------------
I've added a thread to the application manager that will retire the
applications either when you hit a configurable time limit after app has
finished or when the hit a max number per user. How often the thread runs to
check is also configurable. The applications are simply removed from the RM
application map and thus removed from the UI.
The new configs added are:
+ // time(in ms) between when the retire applications thread checks
<name>yarn.server.resourcemanager.retireApps.check.interval</name>
+ // the length of time(in ms) the RM keeps a completed application
<name>yarn.server.resourcemanager.retireApps.keep.period</name>
+ // the maximum number of completed applications per user RM keeps
<name>yarn.server.resourcemanager.retireApps.user.completed.max</name>
> MR279: Fate of finished Applications on RM
> ------------------------------------------
>
> Key: MAPREDUCE-2649
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2649
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Reporter: Thomas Graves
> Assignee: Thomas Graves
> Attachments: MAPREDUCE-2649-patch-mr279.txt
>
>
> Today RM keeps the references of finished application for ever. Though this
> is not sustainable long term, it keeps
> the user experience saner. Users can revisit RM UI and check the status of
> their apps.
> We need to think of purging old references yet keeping the UX sane.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
