You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Ethan Rose (Jira)" <ji...@apache.org> on 2021/10/20 20:34:10 UTC
[jira] [Updated] (HDDS-633) HBase service fails to start with
OzoneFS as defaultFS
[ https://issues.apache.org/jira/browse/HDDS-633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ethan Rose updated HDDS-633:
----------------------------
Target Version/s: 1.3.0 (was: 1.2.0)
I am managing the 1.2.0 release and we currently have more than 600 issues targeted for 1.2.0. I am moving the target field to 1.3.0.
If you are actively working on this jira and believe this should be targeted for the 1.2.0 release, Please reach out to me via Apache email or Slack.
> HBase service fails to start with OzoneFS as defaultFS
> ------------------------------------------------------
>
> Key: HDDS-633
> URL: https://issues.apache.org/jira/browse/HDDS-633
> Project: Apache Ozone
> Issue Type: Improvement
> Components: Ozone Filesystem
> Affects Versions: 0.3.0
> Reporter: Soumitra Sulav
> Priority: Major
>
> Hbase service fails to start when hbase.root-dir is pointing to OzoneFS.
> Below is the exception encountered :
> {code:java}
> 2018-10-10 20:12:52,255 ERROR [master/hcatest-4:17000] 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:1047)
> at org.apache.hadoop.hbase.procedure2.store.wal.WALProcedureStore.recoverLease(WALProcedureStore.java:383)
> at org.apache.hadoop.hbase.procedure2.ProcedureExecutor.start(ProcedureExecutor.java:551)
> at org.apache.hadoop.hbase.master.HMaster.startProcedureExecutor(HMaster.java:1243)
> at org.apache.hadoop.hbase.master.HMaster.startServiceThreads(HMaster.java:1162)
> at org.apache.hadoop.hbase.master.HMaster.finishActiveMasterInitialization(HMaster.java:853)
> at org.apache.hadoop.hbase.master.HMaster.startActiveMasterManager(HMaster.java:2040)
> at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:553)
> at java.lang.Thread.run(Thread.java:745)
> 2018-10-10 20:12:52,256 ERROR [master/hcatest-4:17000] master.HMaster: Master server abort: loaded coprocessors are: []
> 2018-10-10 20:12:52,256 ERROR [master/hcatest-4:17000] master.HMaster: ***** ABORTING master hcatest-4.openstacklocal,17000,1539202359437: Unhandled exception. Starting shutdown. *****{code}
> Above exception was also observed with YARN-atsv2 service as it uses embedded hbase and hence, WALs for storage. When I pointed the storage back to hdfs, exception was gone.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org