hbase启动后HMaster几秒后死掉

Posted 2022-09-10 qixing

通过 http://s128:16010 无法访问Hbase Web端

查看master日志，有报错：

2019-08-30 16:27:35,137 ERROR [master/s128: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:1092)
	at org.apache.hadoop.hbase.procedure2.store.wal.WALProcedureStore.recoverLease(WALProcedureStore.java:424)
	at org.apache.hadoop.hbase.procedure2.ProcedureExecutor.init(ProcedureExecutor.java:576)
	at org.apache.hadoop.hbase.master.HMaster.createProcedureExecutor(HMaster.java:1538)
	at org.apache.hadoop.hbase.master.HMaster.finishActiveMasterInitialization(HMaster.java:956)
	at org.apache.hadoop.hbase.master.HMaster.startActiveMasterManager(HMaster.java:2353)
	at org.apache.hadoop.hbase.master.HMaster.lambda$run$0(HMaster.java:598)
	at java.lang.Thread.run(Thread.java:748)
2019-08-30 16:27:35,145 ERROR [master/s128:16000:becomeActiveMaster] master.HMaster: ***** ABORTING master s128,16000,1567153618183: 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:1092)
	at org.apache.hadoop.hbase.procedure2.store.wal.WALProcedureStore.recoverLease(WALProcedureStore.java:424)
	at org.apache.hadoop.hbase.procedure2.ProcedureExecutor.init(ProcedureExecutor.java:576)
	at org.apache.hadoop.hbase.master.HMaster.createProcedureExecutor(HMaster.java:1538)
	at org.apache.hadoop.hbase.master.HMaster.finishActiveMasterInitialization(HMaster.java:956)
	at org.apache.hadoop.hbase.master.HMaster.startActiveMasterManager(HMaster.java:2353)
	at org.apache.hadoop.hbase.master.HMaster.lambda$run$0(HMaster.java:598)
	at java.lang.Thread.run(Thread.java:748)
2019-08-30 16:27:35,145 INFO  [master/s128:16000:becomeActiveMaster] regionserver.HRegionServer: ***** STOPPING region server ‘s128,16000,1567153618183‘ *****
2019-08-30 16:27:35,146 INFO  [master/s128:16000:becomeActiveMaster] regionserver.HRegionServer: STOPPED: Stopped by master/s128:16000:becomeActiveMaster
2019-08-30 16:27:35,444 INFO  [master/s128:16000.splitLogManager..Chore.1] hbase.ScheduledChore: Chore: SplitLogManager Timeout Monitor was stopped
2019-08-30 16:27:35,978 INFO  [master/s128:16000] ipc.NettyRpcServer: Stopping server on /192.168.3.128:16000

　　解决方法：

在hbase-site.xml中添加如下配置：

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