[
https://issues.apache.org/jira/browse/MAPREDUCE-5386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashwin Shankar updated MAPREDUCE-5386:
--------------------------------------
Affects Version/s: 2.1.0-beta
Status: Patch Available (was: Open)
This patch will not apply now since it depends on MAPREDUCE-5265.
I've created a new option on the history server admin interface :
'-refreshJobRetentionSettings' which will refresh all the three parameters
mentioned in the description.
I've added two unit tests - one tests the job history retention stuff in
isolation and the other tests the RPC communication.
> Refresh job retention time,job cleaner interval, enable/disable cleaner
> -----------------------------------------------------------------------
>
> Key: MAPREDUCE-5386
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5386
> Project: Hadoop Map/Reduce
> Issue Type: Sub-task
> Components: jobhistoryserver
> Affects Versions: 2.1.0-beta
> Reporter: Ashwin Shankar
> Assignee: Ashwin Shankar
> Labels: features
> Attachments: JOB_RETENTION-1.txt
>
>
> We want to be able to refresh following job retention parameters
> without having to bounce the history server :
> 1. Job retention time - mapreduce.jobhistory.max-age-ms
> 2. Cleaner interval - mapreduce.jobhistory.cleaner.interval-ms
> 3. Enable/disable cleaner -mapreduce.jobhistory.cleaner.enable
--
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
