hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Joseph Evans (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-2537) MR-279: The RM writes its log to yarn-mapred-resourcemanager-<RM_Host>.out
Date Fri, 27 May 2011 13:43:47 GMT

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

Robert Joseph Evans commented on MAPREDUCE-2537:

OK I understand now.  The original description of the issue by the person who found it was
very vague.

The issue is that yarn-$YARN_IDENT_STRING-$command-$HOSTNAME.out is where stdout of the command
is placed, and that even though yarn.log.dir, yarn.log.file, and yarn.root.logger system properties
are being set they are not being used by the log4j configuration.  The log4j configuration
defaults to CONSOLE which outputs the logs to stdout which in turn goes to yarn-$YARN_IDENT_STRING-$command-$HOSTNAME.out.

The fix is to either update the log4j conf to use the yarn variants of these variables, or
to set the hadoop equivalents of these variables instead.  I assume from your comment that
we need to switch them over to use the hadoop variants.  Is this correct?

> MR-279: The RM writes its log to yarn-mapred-resourcemanager-<RM_Host>.out
> --------------------------------------------------------------------------
>                 Key: MAPREDUCE-2537
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2537
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2
>            Reporter: Robert Joseph Evans
>            Assignee: Robert Joseph Evans
>            Priority: Minor
>         Attachments: MR-2537-v1.patch

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message