AnsweredAssumed Answered

HBase master will not start after upgrade to MEP 3.0

Question asked by terryhealy on Jun 13, 2017
Latest reply on Jun 15, 2017 by terryhealy

Running community 5.2.0 and attempted to update to MEP 3.0.0 and apparently messed something up. My 3 HBase masters will not start - they are also Zookeepers, which thankfully is fine. A look at the log shows that it thinks the port (16000) is already in use:

 

2017-06-12 14:02:26,770 INFO [main] regionserver.RSRpcServices: master/hd15.sec.bnl.local/192.168.4.15:16000 server-side HConnection retries=350
2017-06-12 14:02:26,934 INFO [main] ipc.SimpleRpcScheduler: Using deadline as user call queue, count=3
2017-06-12 14:02:26,947 ERROR [main] master.HMasterCommandLine: Master exiting
java.lang.RuntimeException: Failed construction of Master: class org.apache.hadoop.hbase.master.HMaster

....

Caused by: java.net.BindException: Address already in use

netstat -tulpn shows nothing on that port.

 

Even the same after a reboot.

I get an error when trying to start it with maprcli:

[root@hd15:/opt/mapr/hbase/hbase-1.1.8/logs]# maprcli node services -hbmaster start -nodes 192.168.4.15
Unable to find mlockall_agent, hbase must be compiled with -Pnative

 

Any suggestions?

 

Thanks

Outcomes