hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arun C Murthy (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-1750) We should log better if something goes wrong with the process fork
Date Mon, 27 Aug 2007 19:11:30 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12523087
] 

Arun C Murthy commented on HADOOP-1750:
---------------------------------------

+1

Ultra-minor nit: I don't like the name 'copyStream', a tad too generic for the specific function
it's doing... oh well!

> We should log better if something goes wrong with the process fork
> ------------------------------------------------------------------
>
>                 Key: HADOOP-1750
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1750
>             Project: Hadoop
>          Issue Type: Improvement
>          Components: mapred
>            Reporter: Owen O'Malley
>            Assignee: Owen O'Malley
>             Fix For: 0.14.1
>
>         Attachments: copy-err.patch
>
>
> Currently, if something goes wrong with bash, the user only gets the error code out.
In the case of error result, we should copy the stdout and stderr from the bash process to
the user logs.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message