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 D9913200CA9 for ; Thu, 1 Jun 2017 16:42:08 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id D80FC160BB5; Thu, 1 Jun 2017 14:42:08 +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 2DBB1160BC4 for ; Thu, 1 Jun 2017 16:42:08 +0200 (CEST) Received: (qmail 33415 invoked by uid 500); 1 Jun 2017 14:42:07 -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 33402 invoked by uid 99); 1 Jun 2017 14:42:07 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Jun 2017 14:42:07 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id D088C1858C8 for ; Thu, 1 Jun 2017 14:42:06 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.502 X-Spam-Level: X-Spam-Status: No, score=-99.502 tagged_above=-999 required=6.31 tests=[KAM_NUMSUBJECT=0.5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id ckLin91gI7xd for ; Thu, 1 Jun 2017 14:42:06 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 6DC7D5FBA4 for ; Thu, 1 Jun 2017 14:42:05 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id D885BE0D9D for ; Thu, 1 Jun 2017 14:42:04 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 2DF9621B5B for ; Thu, 1 Jun 2017 14:42:04 +0000 (UTC) Date: Thu, 1 Jun 2017 14:42:04 +0000 (UTC) From: "Sean Busbey (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HBASE-17996) HBase master fails to start sometimes on RHEL7 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 01 Jun 2017 14:42:09 -0000 [ https://issues.apache.org/jira/browse/HBASE-17996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Busbey updated HBASE-17996: -------------------------------- Component/s: test > HBase master fails to start sometimes on RHEL7 > ---------------------------------------------- > > Key: HBASE-17996 > URL: https://issues.apache.org/jira/browse/HBASE-17996 > Project: HBase > Issue Type: Bug > Components: master, test > Reporter: David Knupp > Attachments: hbase-jenkins-master-impala-boost-static-burst-slave-el7-02f4.vpc.cloudera.com.out, hbase-jenkins-master-impala-boost-static-burst-slave-el7-11ef.vpc.cloudera.com.out > > > Impala includes HBase in its local test environment, and we have found that intermittently, the HBase master node fails to start when we are testing on RHEL7. > In these failures, what we typically see in the logs is this: > {noformat} > 17/04/29 21:33:47 INFO zookeeper.ClientCnxn: Session establishment complete on server localhost/0:0:0:0:0:0:0:1:2181, sessionid = 0x15bbd21b797000a, negotiated timeout = 90000 > 17/04/29 21:33:47 INFO client.ZooKeeperRegistry: ClusterId read in ZooKeeper is null > 17/04/29 21:33:48 INFO master.ActiveMasterManager: Deleting ZNode for /hbase/backup-masters/localhost,16000,1493526758211 from backup master directory > {noformat} > On a successful startup, the log looks like this: > {noformat} > 17/04/16 21:32:29 INFO zookeeper.ClientCnxn: Session establishment complete on server localhost/0:0:0:0:0:0:0:1:2181, sessionid = 0x15b7a2ed6860005, negotiated timeout = 90000 > 17/04/16 21:32:29 INFO client.ZooKeeperRegistry: ClusterId read in ZooKeeper is null > 17/04/16 21:32:30 INFO util.FSUtils: Created version file at hdfs://localhost:20500/hbase with version=8 > 17/04/16 21:32:31 INFO master.MasterFileSystem: BOOTSTRAP: creating hbase:meta region > {noformat} > So the event that we don't see in the failed start up attempts is {{master.MasterFileSystem: BOOTSTRAP: creating hbase:meta region}}. > The full logs will be attached. -- This message was sent by Atlassian JIRA (v6.3.15#6346)