hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sangjin Lee (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-5232) log classpath and other key properties on child JVM start
Date Thu, 09 May 2013 23:34:13 GMT

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

Sangjin Lee commented on MAPREDUCE-5232:
----------------------------------------

I posted the proposed patch. I'm not 100% happy with the config names, and am open to suggestions.
                
> log classpath and other key properties on child JVM start
> ---------------------------------------------------------
>
>                 Key: MAPREDUCE-5232
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5232
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: mrv1, mrv2
>    Affects Versions: 2.0.4-alpha
>            Reporter: Sangjin Lee
>         Attachments: MAPREDUCE-5232-branch-2.patch, MAPREDUCE-5232.patch
>
>
> It would be great if we log vital information such as classpath, etc. upon a mapreduce
child JVM start. This would help a great deal in terms of troubleshooting classpath issues,
etc. Today it is pretty difficult to debug this unless you preserve the container script.
> Maybe it can log things like classpath, os name/version, java version, etc. at the beginning
of the child JVM start.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message