[
https://issues.apache.org/jira/browse/MAPREDUCE-2649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Graves updated MAPREDUCE-2649:
-------------------------------------
Release Note:
The new configs added are:
// time(in ms) between when the expire applications thread checks
<name>yarn.server.resourcemanager.expire.applications.monitor.interval</name>
// the length of time(in ms) the RM keeps a completed application
<name>yarn.server.resourcemanager.expire.applications.interval</name>
// the maximum number of completed applications per user RM keeps
<name>yarn.server.resourcemanager.expire.applications.user.completed.max</name>
was:
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>
Status: Patch Available (was: Open)
> 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
> Fix For: 0.23.0
>
> Attachments: MAPREDUCE-2649-patch-mr279.txt, MAPREDUCE-2649-v2.patch
>
>
> 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
