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

Sangjin Lee updated MAPREDUCE-5232:
-----------------------------------

    Status: Patch Available  (was: Open)

Updated the patches. By the way, the build seems broken on branch-2 currently 
(before this patch).

[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:2.5.1:testCompile 
(default-testCompile) on project hadoop-mapreduce-client-shuffle: Compilation 
failure: Compilation failure:
[ERROR] 
/Users/sjlee/git/hadoop-common/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-shuffle/src/test/java/org/apache/hadoop/mapred/TestShuffleHandler.java:[341,29]
 cannot find symbol
[ERROR] symbol  : variable POSIX
[ERROR] location: class org.apache.hadoop.io.nativeio.NativeIO
[ERROR] 
/Users/sjlee/git/hadoop-common/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-shuffle/src/test/java/org/apache/hadoop/mapred/TestShuffleHandler.java:[357,19]
 join(java.lang.CharSequence,java.lang.Iterable<?>) in 
org.apache.hadoop.util.StringUtils cannot be applied to 
(java.lang.String,java.lang.String[])

                
> 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

Reply via email to