hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-3590) Null pointer exception in JobTracker when the task tracker is not yet resolved
Date Thu, 19 Jun 2008 15:33:45 GMT

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

Hadoop QA commented on HADOOP-3590:
-----------------------------------

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12384265/HADOOP-3590.patch
  against trunk revision 669479.

    +1 @author.  The patch does not contain any @author tags.

    -1 tests included.  The patch doesn't appear to include any new or modified tests.
                        Please justify why no tests are needed for this patch.

    +1 javadoc.  The javadoc tool did not generate any warning messages.

    +1 javac.  The applied patch does not increase the total number of javac compiler warnings.

    +1 findbugs.  The patch does not introduce any new Findbugs warnings.

    +1 release audit.  The applied patch does not increase the total number of release audit
warnings.

    +1 core tests.  The patch passed core unit tests.

    +1 contrib tests.  The patch passed contrib unit tests.

Test results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2696/testReport/
Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2696/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2696/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2696/console

This message is automatically generated.

> Null pointer exception in JobTracker when the task tracker is not yet resolved
> ------------------------------------------------------------------------------
>
>                 Key: HADOOP-3590
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3590
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>            Reporter: Amar Kamat
>            Assignee: Amar Kamat
>            Priority: Blocker
>             Fix For: 0.18.0
>
>         Attachments: HADOOP-3590.patch
>
>
> 2008-06-17 13:29:56,711 INFO org.apache.hadoop.mapred.JobTracker: Got heartbeat from:
xxx (initialContact: false acceptNewTasks: true) with responseId: 0
> 2008-06-17 13:29:56,711 INFO org.apache.hadoop.ipc.Server: IPC Server handler 7 on 123,
call heartbeat(org.apache.hadoop.mapred.TaskTrackerStatus@123, true, true, -1) from xxx error:
java.io.IOException: java.lang.NullPointerException
> java.io.IOException: java.lang.NullPointerException
>        at org.apache.hadoop.mapred.JobTracker.getParentNode(JobTracker.java:1327)
>        at org.apache.hadoop.mapred.JobInProgress.findNewMapTask(JobInProgress.java:1142)
>        at org.apache.hadoop.mapred.JobInProgress.obtainNewMapTask(JobInProgress.java:685)
>        at org.apache.hadoop.mapred.JobTracker.getNewTaskForTaskTracker(JobTracker.java:1708)
>        at org.apache.hadoop.mapred.JobTracker.heartbeat(JobTracker.java:1431)
>        at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
>        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>        at java.lang.reflect.Method.invoke(Method.java:597)
>        at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:452)
>        at org.apache.hadoop.ipc.Server$Handler.run(Server.java:888)
> ----
> Looks like a corner case. This happens when the task tracker just joins the JT and asks
for a task to run. In a case where the task tracker is not yet resolved, this can lead to
null pointer exception. Remember that the task trackers are  added to separate queue and resolved
by a separate thread i.e there is no forced resolution for task trackers. There is no side
effect of this bug since the task tracker will try again and also the job runs to completion.

-- 
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