From core-dev-return-61793-apmail-hadoop-core-dev-archive=hadoop.apache.org@hadoop.apache.org Fri Feb 13 07:22:23 2009 Return-Path: Delivered-To: apmail-hadoop-core-dev-archive@www.apache.org Received: (qmail 8151 invoked from network); 13 Feb 2009 07:22:23 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 13 Feb 2009 07:22:23 -0000 Received: (qmail 71624 invoked by uid 500); 13 Feb 2009 07:22:20 -0000 Delivered-To: apmail-hadoop-core-dev-archive@hadoop.apache.org Received: (qmail 71601 invoked by uid 500); 13 Feb 2009 07:22:20 -0000 Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: core-dev@hadoop.apache.org Delivered-To: mailing list core-dev@hadoop.apache.org Received: (qmail 71590 invoked by uid 99); 13 Feb 2009 07:22:20 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Feb 2009 23:22:20 -0800 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Feb 2009 07:22:19 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id CA002234C48B for ; Thu, 12 Feb 2009 23:21:59 -0800 (PST) Message-ID: <1901535901.1234509719812.JavaMail.jira@brutus> Date: Thu, 12 Feb 2009 23:21:59 -0800 (PST) From: "Matei Zaharia (JIRA)" To: core-dev@hadoop.apache.org Subject: [jira] Updated: (HADOOP-5154) 4-way deadlock in FairShare scheduler In-Reply-To: <1220577910.1233560519552.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HADOOP-5154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matei Zaharia updated HADOOP-5154: ---------------------------------- Attachment: hadoop-5154-v1.patch Here's a new patch taking into account Tom's comments. Tom, the reason I had moved the update outside of the loop was because I thought I might want to acquire a lock on the JobTracker in update later, which could cause a deadlock with assignTasks (which locks the JT and then the scheduler), but now I think that this is not necessary so there's no reason to do it. > 4-way deadlock in FairShare scheduler > ------------------------------------- > > Key: HADOOP-5154 > URL: https://issues.apache.org/jira/browse/HADOOP-5154 > Project: Hadoop Core > Issue Type: Bug > Components: contrib/fair-share > Reporter: Vinod K V > Attachments: FairSchedulerDeadLock.txt, hadoop-5154-v0.patch, hadoop-5154-v1.patch > > > This happened while trying to change the priority of a job from the scheduler servlet. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.