[
https://issues.apache.org/jira/browse/MAPREDUCE-5232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli updated MAPREDUCE-5232:
-----------------------------------------------
Status: Open (was: Patch Available)
Can see the value for this. Some comments on the patch:
- In MRAppMaster, the logging should be done after job.xml is added as a
resource. Otherwise, AppMaster won't pick up this config. Please also test
this manually.
- MRApps: The "***********" marker will look ugly to print after each line. We
should remove this.
- MRJobConfig: MAPREDUCE_CHILD_LOG_PROPERTIES_ON_START isn't just for child.
Rename the constant as well as the config name. It can simply be
"mapreduce.jvm.system-properties-to-log"
- Given above, also fix the description in mapred-default.xml
- Also add a default constant in MRJobConf corresponding to the value in
mapred-default.xml
> 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
