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 "Sangjin Lee (JIRA)" <ji...@apache.org> on 2013/05/10 01:32:13 UTC
[jira] [Updated] (MAPREDUCE-5232) log classpath and other key
properties on child JVM start
[ https://issues.apache.org/jira/browse/MAPREDUCE-5232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sangjin Lee updated MAPREDUCE-5232:
-----------------------------------
Attachment: MAPREDUCE-5232-branch-2.patch
Patch for branch-2
> 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