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/07/01 23:15:20 UTC
[jira] [Commented] (MAPREDUCE-5356) Refresh Log aggregation
'retention period' and 'check interval'
[ https://issues.apache.org/jira/browse/MAPREDUCE-5356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13697182#comment-13697182 ]
Jason Lowe commented on MAPREDUCE-5356:
---------------------------------------
bq. 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.
The nodemanager and historyserver are separate nodes often with separate configs. If we want to support enabling/disabling log aggregation as a rolling change through the grid then we need a way to refresh it. Arguably these should be handled separately, as I'm not thrilled with the prospect of the historyserver knowing about and connecting to all the nodemanagers in the cluster just for this.
IMHO we should keep the ability to update the enable/disable state of log aggregation as part of this change, with the understanding that if someone changes that config and refreshes they know what they're doing wrt. the other nodes in the cluster.
> 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