hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (JIRA)" <j...@apache.org>
Subject [jira] [Moved] (YARN-85) Allow per job log aggregation configuration
Date Wed, 05 Sep 2012 03:34:07 GMT

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

Vinod Kumar Vavilapalli moved MAPREDUCE-3905 to YARN-85:
--------------------------------------------------------

          Component/s:     (was: mrv2)
                       nodemanager
     Target Version/s:   (was: 0.23.3, 2.0.0-alpha, 3.0.0)
    Affects Version/s:     (was: 0.23.0)
                  Key: YARN-85  (was: MAPREDUCE-3905)
              Project: Hadoop YARN  (was: Hadoop Map/Reduce)
    
> Allow per job log aggregation configuration
> -------------------------------------------
>
>                 Key: YARN-85
>                 URL: https://issues.apache.org/jira/browse/YARN-85
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: nodemanager
>            Reporter: Siddharth Seth
>            Assignee: Siddharth Seth
>
> Currently, if log aggregation is enabled for a cluster - logs for all jobs will be aggregated
- leading to a whole bunch of files on hdfs which users may not want.
> Users should be able to control this along with the aggregation policy - failed only,
all, etc.

--
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

Mime
View raw message