ALM-45737 Guardian TokenServer Heap Memory Usage Exceeds the Threshold

Alarm Description

The system checks the heap memory usage of the TokenServer service every 60 seconds. This alarm is generated when the heap memory usage of the TokenServer instance exceeds the threshold for 10 consecutive times.

This alarm is automatically cleared when the system detects that the heap memory usage is less than the threshold.

Alarm Attributes

Alarm Parameters

Impact on the System

If the heap memory of the Guardian TokenServer instance overflows, OBS cannot be accessed.

Possible Causes

The heap memory of the TokenServer instance is overused or the heap memory is inappropriately allocated.

Handling Procedure

Check heap memory usage.

1. Log in to FusionInsight Manager and choose O&M > Alarm > Alarms > ALM-45737 TokenServer Heap Memory Usage Exceeds the Threshold. Check the location information of the alarm and view the host name of the instance for which the alarm is generated.
2. On FusionInsight Manager, choose Cluster > Services > Guardian. On the page that is displayed, click the Instance tab. On this tab page, select the role corresponding to the host name of the instance for which the alarm is generated. Click the drop-down list in the upper right corner of the chart area and choose Customize > CPU and Memory > TokenServer Heap Memory Usage. Then click OK.
3. Check whether the heap memory used by TokenServer reaches the threshold (95% of the maximum heap memory by default).
   • If yes, go to 4.
   • If no, go to 6.

4. On FusionInsight Manager, choose Cluster > Services > Guardian. On the page that is displayed, click the Instance tab. On this tab page, choose TokenServer > Instance Configuration. Click All Configurations, and choose TokenServer > System. Set -Xmx in the GC_OPTS parameter to a larger value based on site requirements and save the configuration.
   

   If this alarm is generated, the heap memory configured for TokenServer cannot meet the heap memory required by the TokenServer process. You are advised to change the value of -Xmx in GC_OPTS to twice that of the heap memory used by TokenServer. You can change the value based on the actual service scenario. Refer to 2 to view the TokenServer heap memory usage.

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 > Log > Download.
7. Expand the Service drop-down list, and select Guardian for the destination 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.