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 "Ravi Teja Ch N V (JIRA)" <ji...@apache.org> on 2011/09/21 06:51:08 UTC

[jira] [Commented] (MAPREDUCE-2754) MR-279: AM logs are incorrectly going to stderr and error messages going incorrectly to stdout

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

Ravi Teja Ch N V commented on MAPREDUCE-2754:
---------------------------------------------

Thanks for the review Vinod...

bq. You will also need to set corresponding log4j properties

Since the issue now is with the MRAppmaster log settings, I think we can reuse the container-log4j.properties which is used by the containers, for MRAppMaster also, which internally uses CLA as hadoop.root.logger.


> MR-279: AM logs are incorrectly going to stderr and error messages going incorrectly to stdout
> ----------------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-2754
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2754
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2
>    Affects Versions: 0.23.0
>            Reporter: Ramya Sunil
>            Assignee: Ravi Teja Ch N V
>            Priority: Blocker
>             Fix For: 0.23.0
>
>         Attachments: MAPREDUCE-2754.patch
>
>
> The log messages for AM container are going into stderr instead of syslog. Also, stderr and stdout roles are reversed.

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