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/23 21:20:49 UTC

[jira] [Updated] (MAPREDUCE-5356) Ability to refresh aggregated log retention period and check interval

     [ https://issues.apache.org/jira/browse/MAPREDUCE-5356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason Lowe updated MAPREDUCE-5356:
----------------------------------

    Summary: Ability to refresh aggregated log retention period and check interval   (was: Refresh Log aggregation 'retention period' and 'check interval' )
    
> Ability to refresh aggregated log 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, MAPREDUCE-5266-4.txt, MAPREDUCE-5356-5.txt, MAPREDUCE-5356-5.txt, WHOLE_PATCH_NOT_TO_BE_CHKEDIN-MAPREDUCE-5356-5.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