[
https://issues.apache.org/jira/browse/HADOOP-2681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12747906#action_12747906
]
Steve Loughran commented on HADOOP-2681:
----------------------------------------
This problem still exists in 0.21 code, not at line 401
// Setup the log4j prop
vargs.add("-Dhadoop.log.dir=" +
new File(System.getProperty("hadoop.log.dir")
).getAbsolutePath());
The value of hadoop.log.dir should be driven by the configuration, not a system
property. That system property could be an default, but it should be sufficient
for a value in the configuration to be defined.
> NullPointerException in TaskRunner.java when system property "hadoop.log.dir"
> is not set
> ----------------------------------------------------------------------------------------
>
> Key: HADOOP-2681
> URL: https://issues.apache.org/jira/browse/HADOOP-2681
> Project: Hadoop Common
> Issue Type: Bug
> Components: conf
> Affects Versions: 0.15.2
> Reporter: Xu Zhang
> Priority: Minor
>
> Currently, NullPointerException exception is thrown on line 321 in
> TaskRunner.java when system property "hadoop.log.dir" is not set. Instead of
> a NullPointerException exception, I expected a default value for
> "hadoop.log.dir" to be used, or to see a more meaningful error message that
> could have helped me figure out what was wrong (like, telling me that I
> needed to set "hadoop.log.dir" and how to do so).
> Here is one instance of such exceptions:
> WARN mapred.TaskRunner: task_200801181719_0001_m_000000_0 Child Error
> java.lang.NullPointerException
> at java.io.File.<init>(File.java:222)
> at org.apache.hadoop.mapred.TaskRunner.run(TaskRunner.java:321)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
