Details
-
Bug
-
Status: Resolved
-
Blocker
-
Resolution: Fixed
-
0.14.1
-
None
-
None
Description
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]$