Return-Path: Delivered-To: apmail-hadoop-core-dev-archive@www.apache.org Received: (qmail 28655 invoked from network); 17 Jan 2009 01:44:33 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 17 Jan 2009 01:44:33 -0000 Received: (qmail 96217 invoked by uid 500); 17 Jan 2009 01:44:30 -0000 Delivered-To: apmail-hadoop-core-dev-archive@hadoop.apache.org Received: (qmail 96187 invoked by uid 500); 17 Jan 2009 01:44:30 -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 96176 invoked by uid 99); 17 Jan 2009 01:44:30 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Jan 2009 17:44:30 -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; Sat, 17 Jan 2009 01:44:20 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 8DF5E234C485 for ; Fri, 16 Jan 2009 17:43:59 -0800 (PST) Message-ID: <337180766.1232156639566.JavaMail.jira@brutus> Date: Fri, 16 Jan 2009 17:43:59 -0800 (PST) From: "Matei Zaharia (JIRA)" To: core-dev@hadoop.apache.org Subject: [jira] Created: (HADOOP-5075) Potential infinite loop in updateMinSlots MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Potential infinite loop in updateMinSlots ----------------------------------------- Key: HADOOP-5075 URL: https://issues.apache.org/jira/browse/HADOOP-5075 Project: Hadoop Core Issue Type: Bug Components: contrib/fair-share Reporter: Matei Zaharia Priority: Blocker Attachments: hadoop-5075.patch We ran into a problem at Facebook where the updateMinSlots loop in the scheduler was repeating infinitely. This might happen if, due to rounding, we are unable to assign the last few slots in a pool. This patch adds a break statement to ensure that the loop exists if it hasn't managed to assign any slots. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.