ALM-23005 Loader Non-Heap Memory Usage Exceeds the Threshold

Alarm Description

The system checks the non-heap memory usage of the Loader service every 30 seconds. This alarm is generated when the non-heap memory usage of the Loader instance exceeds the threshold for 5 consecutive times. This alarm is cleared if the non-heap memory usage is lower than the threshold.

Alarm Attributes

Alarm Parameters

Impact on the System

The Loader page may fail to be accessed and cannot provide services for external systems.

Possible Causes

The non-heap memory of the Loader instance is overused or the non-heap memory is inappropriately allocated.

Handling Procedure

Check non-heap memory usage.

1. 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 Loader Non-Heap Memory Usage Exceeds the Threshold, and view the Location information. Check the name of the instance host for which the alarm is generated.
2. On FusionInsight Manager, choose Cluster > Name of the target cluster > Services > Loader and click the Instance tab. On the displayed page, select the role corresponding to the host name for which the alarm is generated and select Customize from the drop-down list in the upper right corner of the chart area. Choose Memory and select Loader Non-Heap Memory Resource Percentage. Click OK.
3. Check whether the non-heap memory used by Loader reaches the threshold (80% of the maximum non-heap memory by default).
   • If yes, go to 4.
   • If no, go to 6.

4. On FusionInsight Manager, choose Cluster > Name of the desired cluster > Services > Loader. Click Configurations and then the All Configurations tab. On the displayed page, search for LOADER_GC_OPTS. If the -XX: MaxPermSize parameter is not specified, you can set the initial value with -XX: MaxPermSize=256M. If the alarm persists, change the value again by referring to the note. Click Save, and then click OK
   

   Observe the change trend of the non-heap memory used by Loader in the "Loader non-heap memory resource status" monitoring chart. Then change the value of -XX:MaxPermSize to twice the current non-heap memory usage or to another value to meet site requirements.

5. Restart the affected services or instances 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. In the navigation pane on the left, choose Log > Download.
7. Expand the Service drop-down list, and select Loader for the target cluster.
8. 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.
9. Contact O&M engineers and provide the collected logs.

Alarm Clearance

This alarm is automatically cleared after the fault is rectified.

Related Information

None.