Hive Alarms and Triggering Conditions
Hive Alarms
Alarm ID |
Alarm Severity |
Auto Clear |
Alarm Name |
Alarm Type |
---|---|---|---|---|
16000 |
Minor |
TRUE |
Percentage of Sessions Connected to the HiveServer to Maximum Number Allowed Exceeds the Threshold |
Fault alarm |
16001 |
Minor |
TRUE |
Hive Warehouse Space Usage Exceeds the Threshold |
Fault alarm |
16002 |
Minor |
TRUE |
The Successful Hive SQL Operations Lower than The Threshold |
Fault alarm |
16004 |
Critical |
TRUE |
Hive Service Unavailable |
Fault alarm |
Alarm Triggering Scenarios
- 16000: An alarm is triggered when the ratio of the number of sessions connected to HiveServer to the allowed total number of sessions exceeds the threshold. For example, if the number of connected sessions is 9, the allowed total number of sessions is 12, and the threshold is 70%, an alarm is triggered, because 9/12 > 70%.
- 16001: An alarm is triggered when the ratio of HDFS capacities used by Hive to total HDFS capacities allocated to Hive exceeds the threshold. For example, if 500 GB is allocated to Hive, Hive uses 400 GB, and the threshold is 75%, an alarm is triggered, because 400/500 > 75%.
- 16002: An alarm is triggered when SQL execution success rate is lower than the threshold. If two out of four SQL statements are executed successfully and the threshold is 60%, an alarm is triggered, because 2/4 < 60%.
- 16004: An alarm is triggered when the health status of the Hive service changes to Bad.
- FusionInsight Manager: Choose O&M > Alarm > Thresholds to set the alarm threshold, alarm severity, and alarm triggering time range.
- Metrics related to Hive running can be viewed on the Hive monitoring interface.
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