Return-Path: 
 <hdfs-issues-return-69481-apmail-hadoop-hdfs-issues-archive=hadoop.apache.org@hadoop.apache.org>
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 F3AA510EE8
	for <apmail-hadoop-hdfs-issues-archive@minotaur.apache.org>;
 Wed,  9 Oct 2013 08:26:47 +0000 (UTC)
Received: (qmail 35584 invoked by uid 500); 9 Oct 2013 08:26:45 -0000
Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org
Received: (qmail 35539 invoked by uid 500); 9 Oct 2013 08:26:44 -0000
Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:hdfs-issues-help@hadoop.apache.org>
List-Unsubscribe: <mailto:hdfs-issues-unsubscribe@hadoop.apache.org>
List-Post: <mailto:hdfs-issues@hadoop.apache.org>
List-Id: <hdfs-issues.hadoop.apache.org>
Reply-To: hdfs-issues@hadoop.apache.org
Delivered-To: mailing list hdfs-issues@hadoop.apache.org
Received: (qmail 35515 invoked by uid 99); 9 Oct 2013 08:26:42 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Oct 2013 08:26:42 +0000
Date: Wed, 9 Oct 2013 08:26:42 +0000 (UTC)
From: "Steve Loughran (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12672923.1381274911979.37203.1381307202227@arcas>
In-Reply-To: <JIRA.12672923.1381274911979@arcas>
References: <JIRA.12672923.1381274911979@arcas>
Subject: [jira] [Commented] (HDFS-5328) MiniDFSCluster times out at startup
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


    [ https://issues.apache.org/jira/browse/HDFS-5328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13790162#comment-13790162 ] 

Steve Loughran commented on HDFS-5328:
--------------------------------------

not seen this -is the jenkins box under load/memory swap?

regardless, hard coded delays are always brittle, and could be made configurable with a longer timeout. After all, if the minicluster comes up normally the test is no slower, and if it takes >10s to start, the test fails which is far more expensive in terms of human intervention.

Maybe extend the default spinup time to 30s?

> MiniDFSCluster times out at startup
> -----------------------------------
>
>                 Key: HDFS-5328
>                 URL: https://issues.apache.org/jira/browse/HDFS-5328
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 2.1.1-beta
>            Reporter: Alejandro Abdelnur
>
> It seems MiniDFSCluster startup got slower lately and we are observing the following intermittent failure on startup in our jenkins boxes:
> {code}
> java.io.IOException: Timed out waiting for Mini HDFS Cluster to start
> 	at org.apache.hadoop.hdfs.MiniDFSCluster.waitClusterUp(MiniDFSCluster.java:972)
> 	at org.apache.hadoop.hdfs.MiniDFSCluster.initMiniDFSCluster(MiniDFSCluster.java:665)
> 	at org.apache.hadoop.hdfs.MiniDFSCluster.<init>(MiniDFSCluster.java:585)
> 	at org.apache.hadoop.hdfs.MiniDFSCluster.<init>(MiniDFSCluster.java:511)
> {code}
> By looking at the code the {{waitClusterUp()}} has a hardcoded 10secs timeout (10 1 sec waits).
> There are two things we should look at it, make the timeout configurable, and more important, see what has changed to make the startup slower.



--
This message was sent by Atlassian JIRA
(v6.1#6144)