ALM-43022 IndexServer Process GC Time Exceeds the Threshold

Alarm Description

The system checks the GC duration of IndexServer every 60 seconds. A critical alarm is reported when the GC duration exceeds 12 seconds for three consecutive times. A major alarm is reported when the duration exceeds 12 x 0.8 seconds for three consecutive times. To change the threshold, choose O&M > Alarm > Thresholds > Name of the desired cluster > Spark > GC Time > IndexServer Total GC time. This alarm is cleared when the IndexServer GC duration is shorter than or equal to the threshold.

Alarm Attributes

Alarm Parameters

Impact on the System

If the GC duration exceeds the threshold, the performance of the IndexServer process deteriorates, and the process can even be unavailable. As a result, Carbon tasks with indexing enabled are slow or fail to run.

Possible Causes

The heap memory of the IndexServer process is overused or inappropriately allocated, causing frequent occurrence of the GC process.

Handling Procedure

Check the GC time.

1. On FusionInsight Manager, choose O&M > Alarm > Alarms and select the alarm whose ID is 43022. Check the role name and the IP address of the host where the alarm is generated in Location.
2. On FusionInsight Manager, choose Cluster > Name of the desired cluster > Services > Spark > Instance and click the IndexServer for which the alarm is generated to enter the Dashboard page. Click the drop-down menu in the Chart area and choose Customize > GC Time > Garbage Collection (GC) Time of IndexServer from the drop-down list box in the upper right corner and click OK to check whether the GC time is longer than the threshold (default value: 12 seconds).
   • If the threshold is reached, go to 3.
   • If the threshold is not reached, go to 6.

3. On FusionInsight Manager, choose Cluster > Name of the desired cluster > Services > Spark > Configurations > All Configurations > IndexServer > Default. The default value of the SPARK_DRIVER_MEMORY is 4 GB. You can increase the value 1.5 times to its default. If this alarm is still generated occasionally after the adjustment, increase the value by 0.5 times. Double the value if the alarm is reported frequently.
4. Restart all IndexServer instances.
5. Check whether the alarm is cleared 10 minutes later.
   • If the alarm is cleared, no further action is required.
   • If the alarm is not cleared, go to 6.

Collect fault information.

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

Alarm Clearance

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

Related Information

None.