You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Jason Lowe (JIRA)" <ji...@apache.org> on 2013/05/22 18:19:20 UTC
[jira] [Updated] (MAPREDUCE-5266) Ability to refresh retention
settings on history server
[ https://issues.apache.org/jira/browse/MAPREDUCE-5266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason Lowe updated MAPREDUCE-5266:
----------------------------------
Description:
It would be very useful if the job and log retention settings of the history server could be refreshed without restarting the history server. This would include such things as:
* how many to jobs to keep for browsing
* how many jobs to cache
* how long to retain jobs
* how long to retain logs
* how often to check for retention
was:
It would be very useful if the job and log retention settings of the history server could be refreshed without restarting the history server. This would include such things as:
* how many to jobs to keep for browsing
* how many jobs to cache
* how long to retain logs
* how often to check for retention
> Ability to refresh retention settings on history server
> -------------------------------------------------------
>
> Key: MAPREDUCE-5266
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5266
> Project: Hadoop Map/Reduce
> Issue Type: New Feature
> Components: jobhistoryserver
> Affects Versions: 2.0.5-beta
> Reporter: Jason Lowe
>
> It would be very useful if the job and log retention settings of the history server could be refreshed without restarting the history server. This would include such things as:
> * how many to jobs to keep for browsing
> * how many jobs to cache
> * how long to retain jobs
> * how long to retain logs
> * how often to check for retention
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira