Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 44BD9200B43 for ; Tue, 19 Jul 2016 23:50:22 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 43AF5160A5C; Tue, 19 Jul 2016 21:50:22 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 8C8D2160A76 for ; Tue, 19 Jul 2016 23:50:21 +0200 (CEST) Received: (qmail 62331 invoked by uid 500); 19 Jul 2016 21:50:20 -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 62283 invoked by uid 99); 19 Jul 2016 21:50:20 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Jul 2016 21:50:20 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 859402C0D57 for ; Tue, 19 Jul 2016 21:50:20 +0000 (UTC) Date: Tue, 19 Jul 2016 21:50:20 +0000 (UTC) From: "Enis Soztutar (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HBASE-16244) LocalHBaseCluster start timeout should be configurable MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 19 Jul 2016 21:50:22 -0000 [ https://issues.apache.org/jira/browse/HBASE-16244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Enis Soztutar updated HBASE-16244: ---------------------------------- Resolution: Fixed Fix Version/s: (was: 1.1.2) 1.4.0 2.0.0 Status: Resolved (was: Patch Available) I've committed this to branch-1+. Thanks Sid for the patch. I've run the failed tests, and they passed. > LocalHBaseCluster start timeout should be configurable > ------------------------------------------------------ > > Key: HBASE-16244 > URL: https://issues.apache.org/jira/browse/HBASE-16244 > Project: HBase > Issue Type: Bug > Components: hbase > Affects Versions: 1.0.1.1 > Reporter: Siddharth Wagle > Fix For: 2.0.0, 1.4.0 > > Attachments: HBASE-16244.patch > > > *Scenario*: > - Ambari metrics service uses HBase in standalone mode > - On restart of AMS HBase, the Master gives up in 30 seconds due to a hardcoded timeout in JVMClusterUtil > {noformat} > 2016-07-18 19:24:44,199 ERROR [main] master.HMasterCommandLine: Master exiting > java.lang.RuntimeException: Master not active after 30 seconds > at org.apache.hadoop.hbase.util.JVMClusterUtil.startup(JVMClusterUtil.java:194) > at org.apache.hadoop.hbase.LocalHBaseCluster.startup(LocalHBaseCluster.java:445) > at org.apache.hadoop.hbase.master.HMasterCommandLine.startMaster(HMasterCommandLine.java:227) > at org.apache.hadoop.hbase.master.HMasterCommandLine.run(HMasterCommandLine.java:139) > at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:76) > at org.apache.hadoop.hbase.util.ServerCommandLine.doMain(ServerCommandLine.java:126) > at org.apache.hadoop.hbase.master.HMaster.main(HMaster.java:2526) > {noformat} > - On restart the current Master waits to become active and this leads to the timeout being triggered, waiting for a slightly longer time evades this issue. > - The timeout it seems was meant for unit tests > Attached patch allows the timeout to be configured via hbase-site as well as sets it to 5 minutes for clusters started through HMasterCommandLine. -- This message was sent by Atlassian JIRA (v6.3.4#6332)