[
https://issues.apache.org/jira/browse/MAPREDUCE-5232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13656117#comment-13656117
]
Sangjin Lee commented on MAPREDUCE-5232:
----------------------------------------
[~vinodkv] thanks for the input.
* My bad on MRAppMaster. I'll correct the patch for this.
* My reason for adding those lines was to make it look similar to what other
nodes were doing:
[StringUtils.toStartupShutdownString()|http://svn.apache.org/viewvc/hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/util/StringUtils.java?revision=1457122&view=markup].
Also, these marker lines are *not* printed after each line, but only once when
the JVM starts. Did I miss something?
* The rest of the feedback sounds reasonable. Thanks!
I'll incorporate the feedback, and upload new patches.
> 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
> Assignee: Sangjin Lee
> Attachments: MAPREDUCE-5232-branch-2.patch,
> MAPREDUCE-5232-branch-2.patch, MAPREDUCE-5232.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
