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 "Hadoop QA (JIRA)" <ji...@apache.org> on 2013/06/27 21:42: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=13694993#comment-13694993 ] 

Hadoop QA commented on MAPREDUCE-5356:
--------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12589954/MAPREDUCE-5266-2.txt
  against trunk revision .

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3803//console

This message is automatically generated.
                
> 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