[
https://issues.apache.org/jira/browse/MAPREDUCE-754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sreekanth Ramakrishnan updated MAPREDUCE-754:
---------------------------------------------
Attachment: mapreduce-754-wip.patch
Took a look at the issue, talked with Amareshwari also with regards to this.
Putting up a temporary work in progress patch.
The idea of the patch is when a tracker is blacklisted we just set the number
of trackers on the host to zero and not remove from it. The removal from the
map is only done when tracker is lost.
* Refactored a bit of code in {{JobTracker}} so the lost tracker logic can be
unit tested.
* Added a new test case to check lost tracker.
Test case code for integration between lost and black listed tracker needs
further look/work
> 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
> Reporter: Ramya R
> Priority: Minor
> Attachments: mapreduce-754-wip.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.
