Return-Path: Delivered-To: apmail-lucene-hadoop-dev-archive@locus.apache.org Received: (qmail 25396 invoked from network); 30 Nov 2007 18:53:09 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 30 Nov 2007 18:53:09 -0000 Received: (qmail 76811 invoked by uid 500); 30 Nov 2007 18:52:55 -0000 Delivered-To: apmail-lucene-hadoop-dev-archive@lucene.apache.org Received: (qmail 76787 invoked by uid 500); 30 Nov 2007 18:52:55 -0000 Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hadoop-dev@lucene.apache.org Delivered-To: mailing list hadoop-dev@lucene.apache.org Received: (qmail 76736 invoked by uid 99); 30 Nov 2007 18:52:54 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 30 Nov 2007 10:52:54 -0800 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 30 Nov 2007 18:53:04 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id B08B1714231 for ; Fri, 30 Nov 2007 10:52:43 -0800 (PST) Message-ID: <33507158.1196448763719.JavaMail.jira@brutus> Date: Fri, 30 Nov 2007 10:52:43 -0800 (PST) From: "Hairong Kuang (JIRA)" To: hadoop-dev@lucene.apache.org Subject: [jira] Created: (HADOOP-2314) TestBlockReplacement occasionally get into an infinite loop MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org TestBlockReplacement occasionally get into an infinite loop ----------------------------------------------------------- Key: HADOOP-2314 URL: https://issues.apache.org/jira/browse/HADOOP-2314 Project: Hadoop Issue Type: Bug Affects Versions: 0.15.1 Reporter: Hairong Kuang Assignee: Hairong Kuang Fix For: 0.15.2 It turns out that in the case that tests an invalid deletion hint, either the newNode or source may be choosen to be deleted as an exessive replica since both of the nodes are on the same rack. The test assumes that only newNode will be deleted and wait for its deletion. This causes an infinite loop when source is chosen to be deleted. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.