Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
0.20.205.0
-
None
-
None
Description
Dfs calls from streaming seem to fail with the following error:
Exception in thread "main" java.lang.ExceptionInInitializerError at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:57) at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:79) at org.apache.hadoop.fs.FsShell.main(FsShell.java:1895) Caused by: org.apache.commons.logging.LogConfigurationException: User-specified log class 'org.apache.commons.logging.impl.Log4JLogger' cannot be found or is not useable. at org.apache.commons.logging.impl.LogFactoryImpl.discoverLogImplementation(LogFactoryImpl.java:874) at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:604) at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:336) at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:310) at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:685) at org.apache.hadoop.conf.Configuration.<clinit>(Configuration.java:142) ... 3 more
commons-logging-1.1.1.jar is in the classpath. An easy way to reproduce this is, on a secure deploy, "hadoop --config $HADOOP_CONF_DIR jar hadoop-streaming.jar -input <UserInput> -output Out -mapper "hadoop --config $HADOOP_CONF_DIR dfs -help" -reducer NONE"
Attachments
Issue Links
- is blocked by
-
MAPREDUCE-3112 Calling hadoop cli inside mapreduce job leads to errors
- Closed