Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hadoop-dev@lucene.apache.org
Message-ID: <290540396.1143761378150.JavaMail.jira@ajax>
Date: Fri, 31 Mar 2006 00:29:38 +0100 (BST)
From: "Owen O'Malley (JIRA)" <jira@apache.org>
To: hadoop-dev@lucene.apache.org
Subject: [jira] Updated: (HADOOP-100) Inconsistent locking of the
 JobTracker.taskTrackers field
In-Reply-To: <884327691.1143133758862.JavaMail.jira@ajax>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/HADOOP-100?page=all ]

Owen O'Malley updated HADOOP-100:
---------------------------------

    Attachment: task-tracker-table-locking.patch

I made the table private instead of package local.

I also wrapped each of the references to the table with a lock on the table.

There is still a lingering issue with the webapp's use of JobTracker.taskTrackers(). If a status update comes in while the webapp is iterating through the taskTrackers, it will get a ConcurrentModificationException.

> Inconsistent locking of the JobTracker.taskTrackers field
> ---------------------------------------------------------
>
>          Key: HADOOP-100
>          URL: http://issues.apache.org/jira/browse/HADOOP-100
>      Project: Hadoop
>         Type: Bug
>   Components: mapred
>     Versions: 0.1
>     Reporter: Owen O'Malley
>     Assignee: Owen O'Malley
>      Fix For: 0.1
>  Attachments: task-tracker-table-locking.patch
>
> The JobTracker is using an inconsistant lock for protecting taskTrackers, which is the list of current task trackers. Some of the routines lock the JobTracker and others lock the taskTrackers field.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira