Health Status of a HiveServer or MetaStore Instance Is Concerning
Symptom
The health status of the HiveServer or MetaStore instance is Concerning.
Cause Analysis
The HiveServer or MetaStore instance cannot be normally started. For example, when modifying the MetaStore/HiveServer GC parameter, you can view the startup log of the corresponding process, for example, the hiveserver.out(hadoop-omm-jar-192-168-1-18.out) file. The following exception occurs:
Error: Could not find or load main class Xmx2048M
The preceding information indicates that Xmx2048M is used as the startup parameter of the Java process instead of the JVM during the startup of the Java virtual machine. As shown in the following information, the hyphen (-) is deleted mistakenly.
METASTORE_GC_OPTS=Xms1024M Xmx2048M -DIgnoreReplayReqDetect -XX\:CMSFullGCsBeforeCompaction\=1 -XX\:+UseConcMarkSweepGC -XX\:+CMSParallelRemarkEnabled -XX\:+UseCMSCompactAtFullCollection -XX\:+ExplicitGCInvokesConcurrent -server -XX\:MetaspaceSize\=128M -XX\:MaxMetaspaceSize\=256M
Solution
Check the latest changes to detect incorrect settings.
METASTORE_GC_OPTS=Xms1024M -Xmx2048M -DIgnoreReplayReqDetect -XX\:CMSFullGCsBeforeCompaction\=1 -XX\:+UseConcMarkSweepGC -XX\:+CMSParallelRemarkEnabled -XX\:+UseCMSCompactAtFullCollection -XX\:+ExplicitGCInvokesConcurrent -server -XX\:MetaspaceSize\=128M -XX\:MaxMetaspaceSize\=256M
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.
For any further questions, feel free to contact us through the chatbot.
Chatbot