ALM-45003 HetuEngine QAS Disk Capacity Is Insufficient
Alarm Description
The system checks the HetuEngine QAS disk usage every 60 seconds and compares the actual disk usage with the threshold. The disk usage has a default threshold. This alarm is generated if the disk usage exceeds the threshold.
To change the threshold, choose O&M > Alarm > Thresholds. In the service list, choose HetuEngine > Disk > QAS Disk Usage (QAS).
If the Trigger Count is 1, this alarm is cleared when the usage of the HetuEngine QAS disk is less than or equal to the threshold. If the Trigger Count is greater than 1, this alarm is cleared when the disk usage is less than or equal to 80% of the threshold.
Alarm Attributes
Alarm ID |
Alarm Severity |
Alarm Type |
Service Type |
Auto Cleared |
---|---|---|---|---|
45003 |
Critical (default threshold: 95%) Major (default threshold: 80%) |
Quality of service |
HetuEngine |
Yes |
Alarm Parameters
Type |
Parameter |
Description |
---|---|---|
Location Information |
Source |
Specifies the cluster for which the alarm is generated. |
ServiceName |
Specifies the service for which the alarm is generated. |
|
RoleName |
Specifies the role for which the alarm is generated. |
|
HostName |
Specifies the host for which the alarm is generated. |
|
Additional Information |
PartitionName |
Specifies the disk partition for which the alarm is generated. |
Trigger Condition |
Specifies the alarm triggering condition. |
Impact on the System
Data cannot be written to the HetuEngine QAS disk. SQL diagnosis and materialized view recommendation of HetuEngine SQL O&M are unavailable.
Possible Causes
- The alarm threshold is improperly configured.
- The configuration of the HetuEngine QAS disk cannot meet service requirements. The disk usage reaches the upper limit.
Handling Procedure
Check whether the threshold is set properly.
- Log in to FusionInsight Manager and choose O&M > Alarm > Thresholds. In the service list, choose HetuEngine > Disk > QAS Disk Usage (QAS). Check whether the alarm threshold is set properly. The default threshold is 80% of the disk capacity. You can change the threshold as required.
- Click Modify in the Operation column to modify and save the alarm threshold as required.
- Wait 2 minutes and check whether the alarm is cleared.
- If the alarm is cleared, no further action is required.
- If the alarm is not cleared, go to 4.
Check whether the disk usage reaches the upper limit.
- Expand the alarm information, view the information in the Location area, and check the role name and host name of the QAS disk where the alarm is generated.
- Choose Cluster > Services > HetuEngine and click Instance. On the displayed page, click the QAS role name in the alarm information. On the instance page that is displayed, click Chart and check whether the QAS disk usage in the QAS Disk Usage chart exceeds the threshold (80% of the disk capacity by default).
- Log in to the host of the node where the QAS instance reporting the alarm is located as the root user.
- Run the following command to go to the QAS data directory and delete temporary files as required:
cd ${BIGDATA_DATA_HOME}/hetuengine/qas
- Wait 2 minutes and check whether the alarm is cleared.
- If the alarm is cleared, no further action is required.
- If the alarm fails to be cleared, go to 9.
Collect fault information.
- On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
- Expand the Service drop-down list, select HetuEngine for the target cluster, and click OK.
- Expand the Hosts drop-down list. In the Select Host dialog box that is displayed, select the hosts to which the role belongs, and click OK.
- Click the edit icon in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
- Contact O&M engineers and provide the collected logs.
Alarm Clearance
This alarm is automatically cleared after the fault is rectified.
Related Information
None.
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