[jira] [Resolved] (HBASE-17996) HBase master fails to start sometimes on RHEL7

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[jira] [Resolved] (HBASE-17996) HBase master fails to start sometimes on RHEL7

JIRA jira@apache.org

     [ https://issues.apache.org/jira/browse/HBASE-17996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Josh Elser resolved HBASE-17996.
--------------------------------
    Resolution: Won't Fix

Flipped this from "Fixed" to "Won't Fix" to avoid any confusion about whether or not there was a code-change in HBase.

> 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.4.14#64029)
Loading...