Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 6D26310B2D for ; Wed, 25 Sep 2013 16:18:08 +0000 (UTC) Received: (qmail 20691 invoked by uid 500); 25 Sep 2013 16:18:04 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 20581 invoked by uid 500); 25 Sep 2013 16:18:03 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 20546 invoked by uid 99); 25 Sep 2013 16:18:03 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Sep 2013 16:18:02 +0000 Date: Wed, 25 Sep 2013 16:18:02 +0000 (UTC) From: "Nick Dimiduk (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-9655) IntegrationTestMTTR can loop forever on improperly configured clusters 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/HBASE-9655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13777696#comment-13777696 ] Nick Dimiduk commented on HBASE-9655: ------------------------------------- Ha! Do we have style guidelines against this? > IntegrationTestMTTR can loop forever on improperly configured clusters > ---------------------------------------------------------------------- > > Key: HBASE-9655 > URL: https://issues.apache.org/jira/browse/HBASE-9655 > Project: HBase > Issue Type: Test > Components: test > Affects Versions: 0.95.2 > Reporter: Nick Dimiduk > Assignee: Nick Dimiduk > Attachments: HBASE-9655.00.patch > > > IntegrationTestMTTR has a retry loop that can run infinitely. For instance, running the test on a secure cluster as a user who lacks permissions to perform table actions can cause the this scenario. Add another loop counter and bail when a TimingCalable instance throws too many unexpected Exceptions. -- 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