ALM-45739 TokenServer Non-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 non-heap memory usage of the TokenServer instance exceeds the threshold (80% of the maximum memory) for five consecutive times.

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

This section applies only to MRS 3.1.5 or later.

Alarm Attributes

Alarm Parameters

Impact on the System

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

Possible Causes

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

Handling Procedure

Check non-heap memory usage.

1. Log in to Manager and choose O&M > Alarm > Alarms > TokenServer Non-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 Manager, choose Cluster > Services > Guardian. On the page that is displayed, click the Instances 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 Non-Heap Memory Usage. Then click OK.
3. Check whether the non-heap memory used by TokenServer reaches the threshold (80% of the maximum non-heap memory by default).
   • If yes, go to Step 4.
   • If no, go to Step 6.

4. On Manager, choose Cluster > Services > Guardian. On the page that is displayed, click the Instances tab. On this tab page, choose TokenServer > Instance Configuration. Click All Configurations, and choose TokenServer(Role) > Performance. Set -XX:MaxMetaspaceSize in the GC_OPTS parameter to a larger value based on site requirements and save the configuration.
   

   When this alarm is generated, the non-heap memory size configured for the TokenServer instance cannot meet the non-heap memory requirements of the TokenServer process. You are advised to set -XX:MaxMetaspaceSize in the GC_OPTS parameter to 1/8 of the value of -Xmx (or adjust the value based on site requirements). For example, if -Xmx is set to 2 GB, set -XX:MaxMetaspaceSize to 256 MB. If -Xmx is set to 4 GB, set -XX:MaxMetaspaceSize to 512 MB.

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 Step 6.
   

   During service or instance restart, Guardian may fail to be accessed and jobs cannot access OBS.

Collect fault information.

6. On Manager, choose O&M > Log > Download.
7. Expand the Service drop-down list, and select Guardian for the destination 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. Send the collected fault logs to O&M personnel for help.

Alarm Clearance

This alarm is automatically cleared after the fault is rectified.

Related Information

None