解决HBase错误,ERROR: org.apache.hadoop.hbase.PleaseHoldException: Master is initializing

HBase错误日志：

2019-12-23 00:35:05,844 ERROR [Thread-65] master.HMaster: Master failed to complete initialization after 900000ms. Please consider submitting a bug report including a thread dump of this process.
2019-12-23 00:37:19,430 INFO  [node01,16000,1577031599211_splitLogManager__ChoreService_1] master.SplitLogManager$TimeoutMonitor: Chore: SplitLogManager Timeout Monitor missed its start time
2019-12-23 00:42:44,239 WARN  [JvmPauseMonitor] util.JvmPauseMonitor: Detected pause in JVM or host machine (eg GC): pause of approximately 16603ms
No GCs detected
2019-12-23 00:42:44,247 INFO  [node01,16000,1577031599211_splitLogManager__ChoreService_1] master.SplitLogManager$TimeoutMonitor: Chore: SplitLogManager Timeout Monitor missed its start time
2019-12-23 00:42:44,247 WARN  [master/node01/192.168.100.100:16000] util.Sleeper: We slept 18622ms instead of 3000ms, this is likely due to a long garbage collecting pause and it's usually bad, see http://hbase.apache.org/book.html#trouble.rs.runtime.zkexpired
2019-12-23 00:44:42,005 INFO  [node01,16000,1577031599211_splitLogManager__ChoreService_1] master.SplitLogManager$TimeoutMonitor: Chore: SplitLogManager Timeout Monitor missed its start time
2019-12-23 00:44:42,007 WARN  [master/node01/192.168.100.100:16000] util.Sleeper: We slept 15753ms instead of 3000ms, this is likely due to a long garbage collecting pause and it's usually bad, see http://hbase.apache.org/book.html#trouble.rs.runtime.zkexpired
2019-12-23 00:44:42,012 WARN  [JvmPauseMonitor] util.JvmPauseMonitor: Detected pause in JVM or host machine (eg GC): pause of approximately 15135ms
GC pool 'ParNew' had collection(s): count=1 time=15523ms

hbase 报错

安装hbase2.x成功后启动hbase集群输入lsit,version,status均没有问题，且创建表有问题，在网上查了各种资料重启hadoop，重启zookeper，同步时间都没有解决后来发现是我以前安装过其他版本的hbase，所以在zookeeper的节点中存在hbase这个节点hbase集群启动的时候会读取这个目录中的数据导致2.x版本的hbase无法使用创建表命令创建表。

解决办法

[root@node01 bin]# ./zkCli.sh
Connecting to localhost:2181
.....
[zk: localhost:2181(CONNECTED) 0] rmr /hbase
[zk: localhost:2181(CONNECTED) 1] ls
[root@node01 bin]# 

延伸：

类似的，在使用Zookeeper进行管理Kafka集群时，变更集群也可能会出现上述类似问题，解决方案类似，删除原来Kafka在Zookeeper中相应的注册信息，重启Kafka即可解决。

最后，希望可以帮助出现相同问题的小伙伴们顺利爬坑，记得三连哦 ^-^