Return-Path: X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 62D92DCA2 for ; Mon, 10 Sep 2012 15:24:09 +0000 (UTC) Received: (qmail 21827 invoked by uid 500); 10 Sep 2012 15:24:08 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 21700 invoked by uid 500); 10 Sep 2012 15:24:08 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-issues@hadoop.apache.org Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 21604 invoked by uid 99); 10 Sep 2012 15:24:08 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Sep 2012 15:24:07 +0000 Date: Tue, 11 Sep 2012 02:24:07 +1100 (NCT) From: "Eli Collins (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: <2010332779.58164.1347290647998.JavaMail.jiratomcat@arcas> Subject: [jira] [Created] (HDFS-3910) DFSTestUtil#waitReplication should timeout MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Eli Collins created HDFS-3910: --------------------------------- Summary: DFSTestUtil#waitReplication should timeout Key: HDFS-3910 URL: https://issues.apache.org/jira/browse/HDFS-3910 Project: Hadoop HDFS Issue Type: Improvement Components: test Affects Versions: 2.0.0-alpha Reporter: Eli Collins Assignee: Eli Collins DFSTestUtil#waitReplication never times out so test execution fails only when the mvn test executor times out. This leaves a stray test process around, an example is HDFS-3902. Let's make waitReplication do something like bail after it has checked block locations 10 times for one file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira