ALM-45740 TokenServer GC Duration Exceeds the Threshold

Alarm Description

The system checks the GC duration of the TokenServer process every 60 seconds. This alarm is generated when the GC duration of the TokenServer process exceeds the threshold (12 seconds by default) for five consecutive times.

This alarm is automatically cleared when the system detects that the GC duration is less than the threshold.

Alarm Attributes

Alarm Parameters

Impact on the System

TokenServer responds slowly, and OBS cannot be accessed.

Possible Causes

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

Handling Procedure

Check the GC duration.

1. Log in to FusionInsight Manager and choose O&M > Alarm > Alarms > ALM-45740 TokenServer GC Duration 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 and click the drop-down list in the upper right corner of the chart area. Choose Customize > GC > TokenServer GC Duration. Then click OK.
   Figure 1 TokenServer GC Duration
   

3. Check whether the GC duration of the TokenServer process collected every minute exceeds the threshold (12 seconds 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.
   

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

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 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 personnel and provide the collected logs.

Alarm Clearance

This alarm is automatically cleared after the fault is rectified.

Related Information

None