[ https://issues.apache.org/jira/browse/MAPREDUCE-5232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13656405#comment-13656405 ]
Sangjin Lee commented on MAPREDUCE-5232: ---------------------------------------- Looks like the pre-commit build failed for an unrelated reason: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3620/console Is it possible to "re-kick" the pre-commit build? > 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-branch-2.patch, > MAPREDUCE-5232.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