ALM-45283 UserSync Non-Heap Memory Usage Exceeds the Threshold

Alarm Description

The system checks the non-heap memory usage of the UserSync service every 60 seconds. This alarm is generated when the non-heap memory usage of the UserSync instance exceeds the threshold (80% of the maximum memory) for five consecutive times. This alarm is cleared when the non-heap memory usage is less than the threshold.

Alarm Attributes

Alarm Parameters

Impact on the System

The service may break down. Ranger cannot synchronize LDAP user information.

Possible Causes

The non-heap memory of the UserSync process is overused or the non-heap memory is inappropriately allocated.

Handling Procedure

Check non-heap memory usage.

1. On FusionInsight Manager, choose O&M > Alarm > Alarms > ALM-45283 UserSync 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 FusionInsight Manager, choose Cluster > Services > Ranger > Instance. 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 > UserSync Non-Heap Memory Usage. Click OK.
3. Check whether the non-heap memory used by UserSync reaches the threshold (80% of the maximum non-heap memory by default).
   • If yes, go to 4.
   • If no, go to 6.

4. On FusionInsight Manager, choose Cluster > Services > Ranger > Instance > UserSync > Instance Configuration. Click All Configurations, and choose UserSync > System. Set -XX: MaxPermSize in the GC_OPTS parameter to a larger value based on site requirements and click Save to save the configuration.
   

   If this alarm is generated, the non-heap memory size configured for the UserSync instance cannot meet the non-heap memory required by the UserSync process. You are advised to change the -XX:MaxPermSize value of GC_OPTS to twice that of the current non-heap memory size or change the value based on the site requirements.

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 the fault information.

6. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
7. Expand the Service drop-down list, and select Ranger 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

This alarm is automatically cleared after the fault is rectified.

Related Information

None.