Help Center/
MapReduce Service/
Troubleshooting/
Using HBase/
HBase Failed to Start Due to Inappropriate Parameter Settings
Updated on 2022-12-09 GMT+08:00
HBase Failed to Start Due to Inappropriate Parameter Settings
Symptom
After some parameters are modified, HBase cannot be started.
Cause Analysis
- Check the HMaster log (/var/log/Bigdata/hbase/hm/hbase-omm-xxx.log). It is found that the total of hbase.regionserver.global.memstore.size and hfile.block.cache.size is greater than 0.8, which causes the startup failure. Therefore, adjust the parameter values to make sure that the total value is less than 0.8.
- Check the HMaster and RegionServer out logs (/var/log/Bigdata/hbase/hm/hbase-omm-xxx.out/var/log/Bigdata/hbase/rs/hbase-omm-xxx.out). It is found that Unrecognized VM option is displayed.
Unrecognized VM option Error: Could not create the Java Virtual Machine. Error: A fatal exception has occurred. Program will exit.
Check the GC_OPTS parameters. It is found that the parameters contain unnecessary spaces, for example, -D sun.rmi.dgc.server.gcInterval=0x7FFFFFFFFFFFFFE.
Solution
- After the MemStore and cache parameters are modified, the HBase service is restarted successfully.
- After the GC_OPTS parameters are modified, the HBase service is restarted successfully.
Parent topic: Using HBase
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbot