Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Thu, 18 Jul 2013 17:38:51 +0000 (UTC)
From: "Ashwin Shankar (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: <JIRA.12655192.1372356267820.74236.1374169131316@arcas>
In-Reply-To: <JIRA.12655192.1372356267820@arcas>
References: <JIRA.12655192.1372356267820@arcas>
Subject: [jira] [Updated] (MAPREDUCE-5356) Refresh Log aggregation
 'retention period' and 'check interval'
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Ashwin Shankar updated MAPREDUCE-5356:
--------------------------------------

    Attachment: WHOLE_PATCH_NOT_TO_BE_CHKEDIN-MAPREDUCE-5356-5.txt
    
> 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, MAPREDUCE-5266-4.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