ALM-45586 IoTDBServer Heap Memory Usage Exceeds the Threshold¶
Description¶
The system checks the IoTDBServer process status every 60 seconds. The alarm is generated when the heap memory usage of the IoTDBServer process exceeds the threshold (90% of the maximum memory).
Attribute¶
Alarm ID | Alarm Severity | Auto Clear |
|---|---|---|
45586 | Major | Yes |
Parameters¶
Name | Meaning |
|---|---|
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. |
Impact on the System¶
If the available IoTDBServer process heap memory is insufficient, a memory overflow occurs and the service breaks down.
Possible Causes¶
The heap memory of the IoTDBServer process is overused or the heap memory is inappropriately allocated.
Procedure¶
Check the heap memory usage.
Log in to FusionInsight Manager and choose O&M. In the navigation pane on the left, choose Alarm > Alarms. On the page that is displayed, locate the row containing the alarm whose Alarm ID is 45586, view the role name in Location, and check the instance IP address.
Choose Cluster > Name of the desired cluster > Service > IoTDB > Instance. Click the IoTDBServer for which the alarm is generated to go to Dashboard. Click the drop-down list in the upper right corner of the chart area and choose Customize > Memory. In the dialog box that is displayed, select IoTDBServer Heap Memory Resource Percentage, and click OK. Check whether the used non-heap memory of the IoTDBServer process reaches 90% (by default) of the maximum non-heap memory specified for IoTDBServer.
Choose Cluster > Name of the desired cluster > Service > IoTDB > Configuration, click All Configurations, choose IoTDBServer > System, and increase the value of -Xmx in the GC_OPTS parameter.
Note
The default value of -Xmx is 2G.
If this alarm is occasionally generated, increase the value by 0.5 times. If this alarm is frequently generated, double the value.
In the case of large service volume and high service concurrency, you are advised to add instances.
Check whether the alarm is cleared.
If yes, no further action is required.
If no, go to 5.
Collect the 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 IoTDB for the target cluster, and click OK.
Click
in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time respectively. Then, click Download.Contact O&M personnel and provide the collected logs.
Alarm Clearing¶
This alarm is automatically cleared after the fault is rectified.