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 22:40:00 UTC
[jira] Created: (MAPREDUCE-2373) When tasks exit with a nonzero
exit status, task runner should log the stderr as well as stdout
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
[jira] Updated: (MAPREDUCE-2373) When tasks exit with a nonzero
exit status, task runner should log the stderr as well as stdout
Posted by "Todd Lipcon (JIRA)" <ji...@apache.org>.
[ 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
[jira] Updated: (MAPREDUCE-2373) When tasks exit with a nonzero
exit status, task runner should log the stderr as well as stdout
Posted by "Todd Lipcon (JIRA)" <ji...@apache.org>.
[ 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
Sorry, attached wrong patch file. But the above comment stands.
> 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
>
> Attachments: mapreduce-2373-on-20sec.txt
>
>
> 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
[jira] [Commented] (MAPREDUCE-2373) When tasks exit with a nonzero
exit status, task runner should log the stderr as well as stdout
Posted by "Aaron T. Myers (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-2373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13060228#comment-13060228 ]
Aaron T. Myers commented on MAPREDUCE-2373:
-------------------------------------------
The amendment patch looks good, Todd. Thanks for doing that.
> 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
>
> Attachments: mapreduce-2373-on-20sec.txt, mr-2373-amendment.txt
>
>
> 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
[jira] Updated: (MAPREDUCE-2373) When tasks exit with a nonzero
exit status, task runner should log the stderr as well as stdout
Posted by "Todd Lipcon (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-2373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Todd Lipcon updated MAPREDUCE-2373:
-----------------------------------
Attachment: (was: mapreduce-2373-on-20sec.txt)
> 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
[jira] [Updated] (MAPREDUCE-2373) When tasks exit with a nonzero
exit status, task runner should log the stderr as well as stdout
Posted by "Todd Lipcon (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-2373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Todd Lipcon updated MAPREDUCE-2373:
-----------------------------------
Attachment: mr-2373-amendment.txt
here's an amendment to this patch -- the issue is that setPermission can actually throw ExitCodeException, which then caused an NPE in the catch clause.
When this patch is put on trunk/mrv2, we should include this amendment.
> 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
>
> Attachments: mapreduce-2373-on-20sec.txt, mr-2373-amendment.txt
>
>
> 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
[jira] [Updated] (MAPREDUCE-2373) When tasks exit with a nonzero
exit status, task runner should log the stderr as well as stdout
Posted by "Konstantin Shvachko (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-2373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konstantin Shvachko updated MAPREDUCE-2373:
-------------------------------------------
Fix Version/s: (was: 0.22.0)
> 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
> Attachments: mapreduce-2373-on-20sec.txt, mr-2373-amendment.txt
>
>
> 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.
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