hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amar Kamat (JIRA)" <j...@apache.org>
Subject [jira] Commented: (MAPREDUCE-754) NPE in expiry thread when a TT is lost
Date Tue, 08 Dec 2009 16:39:18 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12787567#action_12787567

Amar Kamat commented on MAPREDUCE-754:

bq. test-patch and all tests except TestDFSPermission, TestJobHistory, TestReduceFetch and
TestPermission. I ran TestJobHistory and TestPermission locally again and it passed. TestDFSPermission
failure is unrelated while TestReduceFetch failure is a known issue. 
This is for the patch uploaded for Yahoo!'s distribution of Hadoop.

> NPE in expiry thread when a TT is lost
> --------------------------------------
>                 Key: MAPREDUCE-754
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-754
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: jobtracker
>    Affects Versions: 0.20.1
>            Reporter: Ramya R
>            Assignee: Amar Kamat
>            Priority: Minor
>             Fix For: 0.21.0
>         Attachments: mapreduce-754-v1.1.patch, mapreduce-754-v1.2.patch, mapreduce-754-v2.2-branch-21.patch,
mapreduce-754-v2.2-yahoo.patch, mapreduce-754-v2.2.1-yahoo.patch, mapreduce-754-v2.2.patch,
> NullPointerException is obtained in Tracker Expiry Thread. Below is the exception obtained
in the JT logs 
> {noformat}
> ERROR org.apache.hadoop.mapred.JobTracker: Tracker Expiry Thread got exception: java.lang.NullPointerException
>         at org.apache.hadoop.mapred.JobTracker.updateTaskTrackerStatus(JobTracker.java:2971)
>         at org.apache.hadoop.mapred.JobTracker.access$300(JobTracker.java:104)
>         at org.apache.hadoop.mapred.JobTracker$ExpireTrackers.run(JobTracker.java:381)
>         at java.lang.Thread.run(Thread.java:619)
> {noformat}
> The steps to reproduce this issue are:
> * Blacklist a TT. 
> * Restart it. 
> * The above exception is obtained when the first instance of TT is marked as lost.
> However the above exception does not break any functionality.

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

View raw message