Return-Path: X-Original-To: apmail-hive-dev-archive@www.apache.org Delivered-To: apmail-hive-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 130FEC3C6 for ; Thu, 18 Jul 2013 16:29:00 +0000 (UTC) Received: (qmail 4644 invoked by uid 500); 18 Jul 2013 16:28:54 -0000 Delivered-To: apmail-hive-dev-archive@hive.apache.org Received: (qmail 4454 invoked by uid 500); 18 Jul 2013 16:28:53 -0000 Mailing-List: contact dev-help@hive.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hive.apache.org Delivered-To: mailing list dev@hive.apache.org Received: (qmail 4309 invoked by uid 500); 18 Jul 2013 16:28:51 -0000 Delivered-To: apmail-hadoop-hive-dev@hadoop.apache.org Received: (qmail 4254 invoked by uid 99); 18 Jul 2013 16:28:49 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Jul 2013 16:28:49 +0000 Date: Thu, 18 Jul 2013 16:28:49 +0000 (UTC) From: "Brock Noland (JIRA)" To: hive-dev@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (HIVE-4882) PTest2 via the Cloud Provider doesn't replace bad hosts if an exception occurs MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Brock Noland created HIVE-4882: ---------------------------------- Summary: PTest2 via the Cloud Provider doesn't replace bad hosts if an exception occurs Key: HIVE-4882 URL: https://issues.apache.org/jira/browse/HIVE-4882 Project: Hive Issue Type: Bug Reporter: Brock Noland In PTest2 if there is an exception during a run, we don't replace the bad hosts. Specifically this code in PTest.run should be in a finally block: {noformat} for(HostExecutor hostExecutor : mHostExecutors) { if(hostExecutor.remainingDrones() == 0) { mExecutionContext.addBadHost(hostExecutor.getHost()); } } {noformat} -- 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