ALM-45278 RangerAdmin Direct Memory Usage Exceeds the Threshold

Alarm Description

The system checks the direct memory usage of the RangerAdmin service every 60 seconds. This alarm is generated when the direct memory usage of the RangerAdmin instance exceeds the threshold (80% of the maximum memory) for five consecutive times. This alarm is cleared when the direct memory usage of RangerAdmin is less than or equal to the threshold.

Alarm Attributes

Alarm Parameters

Impact on the System

If the direct memory overflows, the service may break down. As a result, the native UI of Ranger cannot be accessed, and policies cannot be created, modified, or deleted.

Possible Causes

The direct memory of the RangerAdmin instance is overused or the direct memory is inappropriately allocated. As a result, the memory usage exceeds the threshold.

Handling Procedure

Check the direct memory usage.

1. On FusionInsight Manager, choose O&M > Alarm > Alarms > ALM-45278 RangerAdmin Direct 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 > RangerAdmin Direct Memory Usage. Click OK.
3. Check whether the direct memory used by RangerAdmin reaches the threshold (80% of the maximum direct memory by default).
   • If yes, go to 4.
   • If no, go to 6.

4. On FusionInsight Manager, choose Cluster > Services > Ranger > Instance > RangerAdmin > Instance Configuration. Click All Configurations, and choose RangerAdmin > System. Increase the value of -XX:MaxDirectMemorySize in the GC_OPTS parameter based on the site requirements and save the configuration.
   

   If this alarm is generated, the direct memory configured for RangerAdmin cannot meet the direct memory required by the RangerAdmin process. You are advised to check the direct memory usage of RangerAdmin and change the value of -XX:MaxDirectMemorySize in GC_OPTS to the twice of the direct memory used by RangerAdmin. You can change the value based on the actual service scenario. For details, see 2.

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.