ALM-50217 Heap Memory Usage of the FE Node Exceeds the Threshold
Alarm Description
The system checks the heap memory usage of the FE node every 30 seconds. This alarm is generated when the heap memory usage exceeds the threshold (95% by default).
This alarm is cleared when the heap memory usage of the FE node falls below the threshold.
Alarm Attributes
Alarm ID |
Alarm Severity |
Alarm Type |
Service Type |
Auto Cleared |
---|---|---|---|---|
50217 |
Major |
Quality of service |
Doris |
Yes |
Alarm Parameters
Type |
Parameter |
Description |
---|---|---|
Location Information |
Source |
Specifies the cluster or system 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 |
Detail |
Specifies the alarm triggering condition. |
Impact on the System
Task execution and client connection to the FE are affected.
Possible Causes
The FE heap memory is too small.
Handling Procedure
Check heap memory usage.
- Log in to FusionInsight Manager, choose O&M > Alarm > Thresholds, select the name of the desired cluster, and choose Doris > CPU and Memory > Heap memory usage of the FE node (FE).
- Click the edit button next to Trigger Count, change the number based on site requirements, and click OK.
- Click Modify in the Operation column, change the alarm threshold based on site requirements, and click OK.
- On FusionInsight Manager, choose Cluster > Services > Doris > FE > Configurations > All Configurations, search for the FE_GC_OPTS parameter, increase the value of -Xmx as required, click Save, and click OK.
- If this alarm is generated, the heap memory configured for the current Doris instance is not enough for data transmission. You are advised to open the instance monitoring page, display the Doris heap memory resource status monitoring chart, and observe the change trend of the heap memory used by Doris in the monitoring chart. Then change the value of -Xmx to twice the current heap memory usage or to another value to meet site requirements.
- When setting the heap memory, you can set -Xms and -Xmx to approximately the same value to prevent performance deterioration caused by heap size adjustment after each GC.
- The sum of -Xmx and XX:MaxPermSize cannot be greater than the actual physical memory of the node server.
- Restart the affected services or instances and check whether the alarm is cleared.
- If yes, no further action is required.
- If no, go to 4.
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, and select Doris for the target cluster.
- 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