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] [Updated] (MAPREDUCE-5232) log classpath and other key properties on child JVM start
Date Wed, 03 Jun 2015 22:25:38 GMT

     [ https://issues.apache.org/jira/browse/MAPREDUCE-5232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sangjin Lee updated MAPREDUCE-5232:
-----------------------------------
    Target Version/s: 2.8.0

This isn't still merged to branch-2. Can someone merge this to branch-2? Thanks!

> 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
>             Fix For: 3.0.0
>
>         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 was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message