hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Siddharth Seth (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-3905) Allow per job log aggregation configuration
Date Mon, 05 Mar 2012 22:15:57 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-3905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13222663#comment-13222663
] 

Siddharth Seth commented on MAPREDUCE-3905:
-------------------------------------------

In the initial patch, am planning to only support per job enable/disable aggregation. Along
with this - an option to keep the logs on the NM for some time if the job disables aggregation.
Something like FAILED_ONLY will not work very well rightnow - since container exit status
is not necessarily an indication of whether a task completes successfully or not.
                
> Allow per job log aggregation configuration
> -------------------------------------------
>
>                 Key: MAPREDUCE-3905
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3905
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: mrv2
>    Affects Versions: 0.23.0
>            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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message