ALM-45589 ConfigNode Heap Memory Usage Exceeds the Threshold

Alarm Description

The system checks the ConfigNode process status every 60 seconds. The alarm is generated when the heap memory usage of the ConfigNode process exceeds the threshold. This alarm is cleared when the heap memory usage of the ConfigNode process is less than the threshold.

Alarm Attributes

Alarm Parameters

Impact on the System

If the heap memory usage of the ConfigNode process is too high, the performance of the ConfigNode process is affected, and even the ConfigNode process becomes unavailable due to memory overflow.

Possible Causes

The heap memory configured for the node is improper. As a result, the usage exceeds the threshold.

Handling Procedure

Check the heap memory configuration.

1. Log in to FusionInsight Manager, choose O&M > Alarm > Alarms. In the real-time alarm list, click in front of this alarm and view the role name and instance IP address in Location.
2. Choose Cluster > Services > IoTDB. Click Instance, click the ConfigNode corresponding to the IP address obtained in 1, and check whether ConfigNode Heap Memory Usage on the Dashboard tab page reaches the threshold specified for the ConfigNode process.

   If the chart is not displayed, 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 ConfigNode Heap Memory Usage and click OK.

   

   You can choose O&M > Alarm > Threshold Configuration > Name of the desired cluster > IoTDB > Memory > ConfigNode Heap Memory Usage (ConfigNode) to view the threshold.

   • If yes, go to 3.
   • If no, go to 6.

3. Choose Cluster > Services > IoTDB. Click Configurations then All Configurations, click ConfigNode, and choose System. Set -Xmx in GC_OPTS to a larger value and save the configuration.
   

   • The default value of -Xmx is 2G.
   • If this alarm is occasionally generated, increase the value of -Xmx by 0.5 times. If this alarm is frequently generated, double the value of -Xmx.
   • In the case of large service volume and high service concurrency, you are advised to add instances.

4. Click Dashboard. Click Restart Service to restart the IoTDB service for the configuration to take effect.
5. Wait for about 120 seconds and check whether the alarm is cleared.
   • If yes, no further action is required.
   • If no, go to 6.

Collect fault information.

6. On FusionInsight Manager, choose O&M > Log > Download.
7. Expand the Service drop-down list, select IoTDB for the target cluster, and click OK.
8. 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.
9. Click the edit icon 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.
10. Contact O&M engineers and provide the collected logs.

Alarm Clearance

This alarm is automatically cleared after the fault is rectified.

Related Information

None.