[
https://issues.apache.org/jira/browse/MAPREDUCE-5356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695254#comment-13695254
]
Devaraj K commented on MAPREDUCE-5356:
--------------------------------------
bq. I just figured that it made sense to add the LOG_AGGREGATION_ENABLED
property(yarn.log-aggregation-enable) to be refreshed along with other two
props mentioned in my first comment.
Node Manager also uses this property and does log aggregation based in this
property. If we change dynamically for History Server, it leads to
inconsistency between NM & HS.
> 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, MAPREDUCE-5266-3.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
