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 "Todd Lipcon (JIRA)" <ji...@apache.org> on 2011/03/09 23:52:59 UTC

[jira] Updated: (MAPREDUCE-2373) When tasks exit with a nonzero exit status, task runner should log the stderr as well as stdout

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

Todd Lipcon updated MAPREDUCE-2373:
-----------------------------------

    Attachment: mapreduce-2373-on-20sec.txt

This part of the code is entirely redone by MAPREDUCE-2178, so no sense in putting a trunk patch here. It will just make that merge harder. This patch is against the "secure 20" code base. I will update it for trunk once 2178 is done.

> When tasks exit with a nonzero exit status, task runner should log the stderr as well as stdout
> -----------------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-2373
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2373
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>    Affects Versions: 0.22.0
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>             Fix For: 0.22.0
>
>
> Currently, if the taskjvm.sh script fails to exec java for some reason, it prints its error message to stderr. This doesn't make it to the logs anywhere. Logging the stderr is very useful to understand why taskjvm.sh failed to start the Child jvm.

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