hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doug Cutting (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-1750) We should log better if something goes wrong with the process fork
Date Wed, 29 Aug 2007 19:16:31 GMT

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

Doug Cutting updated HADOOP-1750:
---------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 0.14.1)
                   0.15.0
           Status: Resolved  (was: Patch Available)

I just committed this.  Thanks, Owen!

Does this really need to be in 0.14.1?  I've changed the fix version to 0.15.0, but if folks
disagree I will set it back to 0.15.1, move the change message to the appropriate section
of CHANGES.txt, and merge it to the branch.  Thoughts?

> 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.15.0
>
>         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