hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (JIRA)" <j...@apache.org>
Subject [jira] Created: (MAPREDUCE-1342) Potential JT deadlock in faulty TT tracking
Date Tue, 29 Dec 2009 02:06:29 GMT
Potential JT deadlock in faulty TT tracking

                 Key: MAPREDUCE-1342
                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1342
             Project: Hadoop Map/Reduce
          Issue Type: Bug
          Components: jobtracker
    Affects Versions: 0.22.0
            Reporter: Todd Lipcon

JT$FaultyTrackersInfo.incrementFaults first locks potentiallyFaultyTrackers, and then calls
blackListTracker, which calls removeHostCapacity, which locks JT.taskTrackers
On the other hand, JT.blacklistedTaskTrackers() locks taskTrackers, then calls faultyTrackers.isBlacklisted()
which goes on to lock potentiallyFaultyTrackers.

I haven't produced such a deadlock, but the lock ordering here is inverted and therefore could

Not sure if this goes back to 0.21 or just in trunk.

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

View raw message