hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eli Collins (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-3692) yarn-resourcemanager out and log files can get big
Date Fri, 20 Jan 2012 00:14:41 GMT

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

Eli Collins commented on MAPREDUCE-3692:
----------------------------------------

bq. What I think we should do is to remove the logging from all handle methods, and selectively
log in the individual transitions that we think are important.

+1 to selectively logging the transitions relating to failures.  The logging in all handle
methods is probably worth keeping at the debug level.
                
> yarn-resourcemanager out and log files can get big
> --------------------------------------------------
>
>                 Key: MAPREDUCE-3692
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3692
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: mrv2
>            Reporter: Eli Collins
>            Assignee: Eli Collins
>            Priority: Blocker
>             Fix For: 0.23.1
>
>         Attachments: mapreduce-3692.txt
>
>
> I'm seeing 8gb resourcemanager out files and big log files, seeing lots of repeated logs
(eg every rpc call or event) looks like we're being too verbose in  a couple of places.

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