ALM-43021 Direct Memory Usage of the IndexServer2x Process Exceeds the Threshold

Description

The system checks the IndexServer2x process status every 30 seconds. The alarm is generated when the direct heap memory usage of a IndexServer2x process exceeds the threshold (95% of the maximum memory).

In MRS 3.3.0-LTS and later versions, the Spark2x component is renamed Spark, and the role names in the component are also changed. For example, IndexServer2x is changed to IndexServer. Refer to the descriptions and operations related to the component name and role names in the document based on your MRS version.

Attribute

Parameters

Impact on the System

If the available IndexServer2x process direct memory is insufficient, a memory overflow occurs and the service breaks down.

Possible Causes

The direct heap memory of the IndexServer2x process is overused or the direct heap memory is inappropriately allocated.

Procedure

Check direct heap memory usage.

1. On FusionInsight Manager, choose O&M > Alarm > Alarms. In the displayed alarm list, choose the alarm for which the ID is 43021, and check the RoleName in Location and confirm the IP address of HostName.
2. On FusionInsight Manager, choose Cluster > Name of the desired cluster > Services > Spark2x > Instance. Click the IndexServer2x that reported the alarm to go to the Dashboard page. Click the drop-down list in the upper right corner of the chart area, and choose Customize > Memory > IndexServer2x Memory Usage Statistics > OK. Check whether the direct memory used by the IndexServer2x process reaches the maximum direct memory threshold.
   • If the threshold is reached, go to 3.
   • If the threshold is not reached, go to 7.
   Figure 1 IndexServer2x Memory Usage Statistics
   

3. On FusionInsight Manager, choose Cluster > Name of the desired cluster > Services > Spark2x > Instance. Click the IndexServer2x that reported the alarm to go to the Dashboard page. Click the drop-down list in the upper right corner of the chart area, and choose Customize > Memory > Direct Memory of IndexServer2x > OK. Based on the alarm generation time, check the values of the used direct memory of the IndexServer2x process in the corresponding period and obtain the maximum value.
   Figure 2 Direct Memory of IndexServer2x
   

4. On FusionInsight Manager, choose Cluster > Name of the desired cluster > Services > Spark2x > Configurations > All Configurations > IndexServer2x> Tuning. You can change the value of XX:MaxDirectMemorySize (the default value is 512 MB) in the spark.driver.extraJavaOptions parameter based on the ratio of the maximum direct memory used by the IndexServer2x process to the threshold specified by IndexServer2x Direct Memory Usage Statistics (IndexServer2x) in the alarm period. If the alarm persists after the parameter value is changed, increase the value by 0.5 times. If the alarm is generated frequently, double the rate.
   

   On FusionInsight Manager, you can choose O&M > Alarm > Thresholds > Name of the desired cluster > Spark2x > Memory > IndexServer2x Direct Memory Usage Statistics (IndexServer2x) to view the threshold.

5. Restart all IndexServer2x instances.
6. After 10 minutes, check whether the alarm is cleared.
   • If the alarm is cleared, no further action is required.
   • If the alarm is not cleared, go to 7.

Collect fault information.

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

Alarm Clearing

After the fault is rectified, the system automatically clears this alarm.

Reference

None