[
https://issues.apache.org/jira/browse/MAPREDUCE-5356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashwin Shankar updated MAPREDUCE-5356:
--------------------------------------
Attachment: MAPREDUCE-5266-2.txt
Note: This patch depends on MAPREDUCE-5265 and will not apply now. HadoopQA
will complain.
Summary:I have added a new command '-refreshLogSettings' to the history server
admin interface which would refresh both:
1.log retention period(yarn.log-aggregation.retain-seconds)
2. check interval(yarn.log-aggregation.retain-check-interval-seconds)
I created a single command for both the properties because :
1. Both properties are related. More often than not,if we change one of them we
would change the other.
2.it seemed better from a usability perspective since the user needs to execute
just one command for both the log properties instead of two separate commands.
I've added two tests - one tests AggregatedLogDeletionService in isolation and
validates if the refreshLogSettings is working properly. The other test
validates the rpc communication between the job history client and server for
this new protocol.
> Refresh Log aggregation 'retention period' and 'check interval'
> ----------------------------------------------------------------
>
> Key: MAPREDUCE-5356
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5356
> 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: MAPREDUCE-5266-2.txt
>
>
> We want to be able to refresh log aggregation retention time
> and 'check interval' time on the fly by changing configs so that we dont have
> to bounce history server.
--
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
