You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Owen O'Malley (JIRA)" <ji...@apache.org> on 2007/10/01 22:08:51 UTC
[jira] Commented: (HADOOP-1977) hadoop job -kill , -status causes
NullPointerException
[ https://issues.apache.org/jira/browse/HADOOP-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531615 ]
Owen O'Malley commented on HADOOP-1977:
---------------------------------------
I looked at this problem. It stems from the fact that JobClient creates a new JobConf rather than use the Configuration from ToolBase. It would be nice to have a version of the CLI parsing library that wasn't based on ToolBase and OO inheritance, since clearly part of what happened here was too much OO magic not making the required usage clear.
> hadoop job -kill , -status causes NullPointerException
> ------------------------------------------------------
>
> Key: HADOOP-1977
> URL: https://issues.apache.org/jira/browse/HADOOP-1977
> Project: Hadoop
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.14.1
> Reporter: lohit vijayarenu
> Priority: Blocker
> Fix For: 0.14.2
>
>
> hadoop job -kill/-status seems to cause NullPointerException
> As an example, I started a streaming job and tried to kill it. This raises NullPointerException
> [lohit@krygw1000 mapred]$ bin/hadoop job -Dmapred.job.tracker=kry1443:56225 -kill job_200710011856_0001
> 07/10/01 18:57:07 INFO jvm.JvmMetrics: Initializing JVM Metrics with processName=JobTracker, sessionId=
> Exception in thread "main" java.lang.NullPointerException
> at org.apache.hadoop.mapred.LocalJobRunner$Job.access$600(LocalJobRunner.java:51)
> at org.apache.hadoop.mapred.LocalJobRunner.getJobStatus(LocalJobRunner.java:296)
> at org.apache.hadoop.mapred.JobClient.getJob(JobClient.java:512)
> at org.apache.hadoop.mapred.JobClient.run(JobClient.java:791)
> at org.apache.hadoop.util.ToolBase.doMain(ToolBase.java:187)
> at org.apache.hadoop.mapred.JobClient.main(JobClient.java:827)
> [lohit@krygw1000 mapred]$
> So does 'hadoop job -status'
> [lohit@krygw1000 mapred]$hadoop job -Dmapred.job.tracker=kry1443:56225 -status job_200710011856_0001
> 07/10/01 18:57:21 INFO jvm.JvmMetrics: Initializing JVM Metrics with processName=JobTracker, sessionId=
> Exception in thread "main" java.lang.NullPointerException
> at org.apache.hadoop.mapred.LocalJobRunner$Job.access$600(LocalJobRunner.java:51)
> at org.apache.hadoop.mapred.LocalJobRunner.getJobStatus(LocalJobRunner.java:296)
> at org.apache.hadoop.mapred.JobClient.getJob(JobClient.java:512)
> at org.apache.hadoop.mapred.JobClient.run(JobClient.java:782)
> at org.apache.hadoop.util.ToolBase.doMain(ToolBase.java:187)
> at org.apache.hadoop.mapred.JobClient.main(JobClient.java:827)
> [lohit@krygw1000 mapred]$
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.