hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-3438) NPE if job tracker started and system property hadoop.log.dir is not set
Date Fri, 23 May 2008 11:33:56 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-3438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12599336#action_12599336
] 

Steve Loughran commented on HADOOP-3438:
----------------------------------------

Root cause is in JobHistory.init. It tries to get the configuration option fo the job history,
but to give it a useful default the system property "hadoop.job.history.location"  is used.
If that property is not set, ops get a support call.


  public static boolean init(JobConf conf, String hostname){
    try {
      LOG_DIR = conf.get("hadoop.job.history.location" ,
        "file:///" + new File(
        System.getProperty("hadoop.log.dir")).getAbsolutePath()
        + File.separator + "history");

> NPE if job tracker started and system property hadoop.log.dir is not set
> ------------------------------------------------------------------------
>
>                 Key: HADOOP-3438
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3438
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: metrics
>    Affects Versions: 0.18.0
>         Environment: amd64 ubuntu, jrockit 1.6
>            Reporter: Steve Loughran
>
> This is a regression. If the system property "hadoop.log.dir" is not set, the job tracker
NPEs rather than starts up.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message