HBase之——部署经验与坑总结

转载请注明出处：https://blog.csdn.net/l1028386804/article/details/88696276

1.本地单机部署hbase,想要使用独立zookeeper,不使用自带的

vim conf/hbase-env.sh
export HBASE_MANAGES_ZK=false

设置不使用自带zookeeper,但是总是报错:

Could not start ZK at requested port of 2181.  ZK was started at port: 2182.  Aborting as clients (e.g. shell) will not be able to find this ZK quorum.

很明显,这是启动自带zookeeper与独立zookeeper冲突了。需要将hbase-site.xml中的hbase.cluster.distributed设置为true。

hbase-site.xml增加配置：

<property>
	<name>hbase.cluster.distributed</name>
	<value>true</value> 
</property>

2.idea javaapi 连接本地hbase超时

hbase-site.xml增加配置：

<property>
	<name>hbase.master.ipc.address</name>
	<value>0.0.0.0</value>
</property>
<property>
	<name>hbase.regionserver.ipc.address</name>
	<value>0.0.0.0</value>
</property>

3.如下异常

2019-03-20 18:27:20,649 ERROR [master/liuyazhuang11:16000:becomeActiveMaster] master.HMaster: Failed to become active master
java.lang.IllegalStateException: The procedure WAL relies on the ability to hsync for proper operation during component failures, but the underlying filesystem does not support doing so. Please check the config value of 'hbase.procedure.store.wal.use.hsync' to set the desired level of robustness and ensure the config value of 'hbase.wal.dir' points to a FileSystem mount that can provide it.
        at org.apache.hadoop.hbase.procedure2.store.wal.WALProcedureStore.rollWriter(WALProcedureStore.java:1086)
        at org.apache.hadoop.hbase.procedure2.store.wal.WALProcedureStore.recoverLease(WALProcedureStore.java:423)
        at org.apache.hadoop.hbase.procedure2.ProcedureExecutor.init(ProcedureExecutor.java:611)
        at org.apache.hadoop.hbase.master.HMaster.createProcedureExecutor(HMaster.java:1458)
        at org.apache.hadoop.hbase.master.HMaster.finishActiveMasterInitialization(HMaster.java:890)
        at org.apache.hadoop.hbase.master.HMaster.startActiveMasterManager(HMaster.java:2272)
        at org.apache.hadoop.hbase.master.HMaster.lambda$run$0(HMaster.java:581)
        at java.lang.Thread.run(Thread.java:748)
2019-03-20 18:27:20,651 ERROR [master/liuyazhuang11:16000:becomeActiveMaster] master.HMaster: ***** ABORTING master liuyazhuang11,16000,1553077635748: Unhandled exception. Starting shutdown. *****
java.lang.IllegalStateException: The procedure WAL relies on the ability to hsync for proper operation during component failures, but the underlying filesystem does not support doing so. Please check the config value of 'hbase.procedure.store.wal.use.hsync' to set the desired level of robustness and ensure the config value of 'hbase.wal.dir' points to a FileSystem mount that can provide it.
        at org.apache.hadoop.hbase.procedure2.store.wal.WALProcedureStore.rollWriter(WALProcedureStore.java:1086)
        at org.apache.hadoop.hbase.procedure2.store.wal.WALProcedureStore.recoverLease(WALProcedureStore.java:423)
        at org.apache.hadoop.hbase.procedure2.ProcedureExecutor.init(ProcedureExecutor.java:611)
        at org.apache.hadoop.hbase.master.HMaster.createProcedureExecutor(HMaster.java:1458)
        at org.apache.hadoop.hbase.master.HMaster.finishActiveMasterInitialization(HMaster.java:890)
        at org.apache.hadoop.hbase.master.HMaster.startActiveMasterManager(HMaster.java:2272)
        at org.apache.hadoop.hbase.master.HMaster.lambda$run$0(HMaster.java:581)
        at java.lang.Thread.run(Thread.java:748)

重点是下面的信息：

java.lang.IllegalStateException: The procedure WAL relies on the ability to hsync for proper operation during component failures, but the underlying filesystem does not support doing so. Please check the config value of 'hbase.procedure.store.wal.use.hsync' to set the desired level of robustness and ensure the config value of 'hbase.wal.dir' points to a FileSystem mount that can provide it.

hbase-site.xml增加配置

<property>
	<name>hbase.unsafe.stream.capability.enforce</name>
	<value>false</value>
</property>