null pointer exception and invocationtarget exception in jobtracker logs
------------------------------------------------------------------------
Key: MAPREDUCE-4038
URL: https://issues.apache.org/jira/browse/MAPREDUCE-4038
Project: Hadoop Map/Reduce
Issue Type: Bug
Components: jobtracker
Affects Versions: 0.20.1
Environment: Cluster with 10 nodes, Linux operating system
Reporter: gan
Priority: Critical
I have written the code for scheduling in hadoop in which i have written two
function schedule() and call() the schedule function calls the resource
calculator for knowing the CPU usage and reliability values(explicitly i gave)
but i am getting null pointer exception in the end. even i have written the
code for getting active tracker names it shows null pointer exception. help me!
ERROR IN JOB TRACKER LOG FILE
2012-03-12 14:37:01,198 INFO org.apache.hadoop.mapred.JobTracker: STARTUP_MSG:
/************************************************************
STARTUP_MSG: Starting JobTracker
STARTUP_MSG: host = slavenode2.yahoo/192.168.1.2
STARTUP_MSG: args = []
STARTUP_MSG: version = 0.20.1
STARTUP_MSG: build =
http://svn.apache.org/repos/asf/hadoop/common/tags/release-0.20.1-rc1 -r
810220; compiled by 'oom' on Tue Sep 1 20:55:56 UTC 2009
************************************************************/
2012-03-12 14:37:01,451 INFO org.apache.hadoop.mapred.JobTracker: Scheduler
configured with (memSizeForMapSlotOnJT, memSizeForReduceSlotOnJT,
limitMaxMemForMapTasks, limitMaxMemForReduceTasks) (-1, -1, -1, -1)
2012-03-12 14:37:01,515 INFO org.apache.hadoop.mapred.resourcecalculator:
192.168.1.2 CPU usage: 0.0
2012-03-12 14:37:01,532 INFO org.apache.hadoop.mapred.resourcecalculator:
192.168.1.3 CPU usage: 0.0
2012-03-12 14:37:01,546 INFO org.apache.hadoop.mapred.resourcecalculator:
192.168.1.4 CPU usage: 0.0
2012-03-12 14:37:01,556 INFO org.apache.hadoop.mapred.resourcecalculator:
192.168.1.5 CPU usage: 0.0
2012-03-12 14:37:01,566 INFO org.apache.hadoop.mapred.resourcecalculator:
192.168.1.7 CPU usage: 0.0
2012-03-12 14:37:01,579 INFO org.apache.hadoop.mapred.resourcecalculator:
192.168.1.8 CPU usage: 0.0
2012-03-12 14:37:01,589 INFO org.apache.hadoop.mapred.resourcecalculator:
192.168.1.11 CPU usage: 0.0
2012-03-12 14:37:01,599 INFO org.apache.hadoop.mapred.resourcecalculator:
192.168.1.12 CPU usage: 0.0
2012-03-12 14:37:01,615 INFO org.apache.hadoop.mapred.resourcecalculator:
192.168.1.254 CPU usage: 0.0
2012-03-12 14:37:01,616 FATAL org.apache.hadoop.mapred.JobTracker:
java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
at
org.apache.hadoop.util.ReflectionUtils.newInstance(ReflectionUtils.java:115)
at org.apache.hadoop.mapred.JobTracker.<init>(JobTracker.java:1573)
at org.apache.hadoop.mapred.JobTracker.startTracker(JobTracker.java:180)
at org.apache.hadoop.mapred.JobTracker.startTracker(JobTracker.java:172)
at org.apache.hadoop.mapred.JobTracker.main(JobTracker.java:3699)
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at
org.apache.hadoop.util.ReflectionUtils.newInstance(ReflectionUtils.java:113)
... 4 more
Caused by: java.lang.NullPointerException
at
org.apache.hadoop.mapred.JobQueueTaskScheduler1.schedule(JobQueueTaskScheduler1.java:75)
at
org.apache.hadoop.mapred.JobQueueTaskScheduler1.call(JobQueueTaskScheduler1.java:139)
at
org.apache.hadoop.mapred.JobQueueTaskScheduler1.<init>(JobQueueTaskScheduler1.java:50)
... 9 more
2012-03-12 14:37:01,617 INFO org.apache.hadoop.mapred.JobTracker: SHUTDOWN_MSG:
/************************************************************
SHUTDOWN_MSG: Shutting down JobTracker at slavenode2.yahoo/192.168.1.2
************************************************************/
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
