根據[1]中的兼容矩陣，如下:

我們采用

hadoop3.1.2

hbase2.2.4

進行測試

$HBASE_HOME/logs/hbase-appleyuchi-master-Desktop.log

報錯:

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:586)at org.apache.hadoop.hbase.master.HMaster.createProcedureExecutor(HMaster.java:1523)at org.apache.hadoop.hbase.master.HMaster.finishActiveMasterInitialization(HMaster.java:938)at org.apache.hadoop.hbase.master.HMaster.startActiveMasterManager(HMaster.java:2124)at org.apache.hadoop.hbase.master.HMaster.lambda$run$0(HMaster.java:580)at java.lang.Thread.run(Thread.java:748) 2020-05-20 20:01:41,447 ERROR [master/Desktop:16000:becomeActiveMaster] master.HMaster: ***** ABORTING master desktop,16000,1589976098311: 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:586)at org.apache.hadoop.hbase.master.HMaster.createProcedureExecutor(HMaster.java:1523)at org.apache.hadoop.hbase.master.HMaster.finishActiveMasterInitialization(HMaster.java:938)at org.apache.hadoop.hbase.master.HMaster.startActiveMasterManager(HMaster.java:2124)at org.apache.hadoop.hbase.master.HMaster.lambda$run$0(HMaster.java:580)at java.lang.Thread.run(Thread.java:748)

根據[1]

hbase.unsafe.stream.capability.enforce=false存在丟失數據的風險，根本無法用于生產環境。

根據[2]中進行自行編譯后(鏈接中是3.2.1的，記得要改成3.1.2)，

hbase.unsafe.stream.capability.enforce=true

下上述報錯消失。

所以官網聲稱的兼容的意思是:

這個兼容包含了你自己編譯的版本，并不是指從官網下載的就一定100%兼容。

?

Reference:

[1]HBase 2.2.2 on Hadoop 3.2.1源碼編譯

[2]編譯hbase2.2.4+hadoop3.2.1

總結

以上是生活随笔為你收集整理的hbase官方网站声称的兼容是否是100%兼容？的全部內容，希望文章能夠幫你解決所遇到的問題。

如果覺得生活随笔網站內容還不錯，歡迎將生活随笔推薦給好友。