Help Center > > User Guide> FusionInsight Manager Operation Guide (Applicable to 3.x)> Alarm Reference (Applicable to MRS 3.x)> ALM-45279 RangerAdmin Non Heap Memory Usage Exceeds the Threshold

ALM-45279 RangerAdmin Non Heap Memory Usage Exceeds the Threshold

Updated at: Oct 21, 2021 GMT+08:00

Description

The system checks the non-heap memory usage of the RangerAdmin service every 60 seconds. This alarm is generated when the non-heap memory usage of the RangerAdmin 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.

Attribute

Alarm ID

Alarm Severity

Auto Clear

45279

Major

Yes

Parameters

Name

Meaning

Source

Specifies the cluster for which the alarm is generated.

ServiceName

Specifies the name of the service for which the alarm is generated.

RoleName

Specifies the name of the role for which the alarm is generated.

HostName

Specifies the name of the host for which the alarm is generated.

Trigger Condition

Specifies the threshold for triggering the alarm.

Impact on the System

Non-heap memory overflow may cause service breakdown.

Possible Causes

The non-heap memory usage of the RangerAdmin instance is high or the non-heap memory is improperly allocated.

Procedure

Check non-heap memory usage.

  1. On FusionInsight Manager, choose O&M > Alarm > Alarms > ALM-45279 RangerAdmin 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 > RangerAdmin Non Heap Memory Usage. Click OK.

    Figure 1 RangerAdmin non-heap memory usage

  3. Check whether the non-heap memory used by RangerAdmin 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 > RangerAdmin > Instance Configuration. Click All Configurations, and choose RangerAdmin > System. Increase the value of -XX: MaxPermSize in the GC_OPTS parameter based on the site requirements and save the configuration.

    If this alarm is generated, the non-heap memory size configured for the RangerAdmin instance cannot meet the non-heap memory required by the RangerAdmin process. You are advised to change the value of -XX:MaxPermSize in GC_OPTS to the twice of the current non-heap memory usage 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.

  1. On the FusionInsight Manager portal, choose O&M > Log > Download.
  2. Expand the Service drop-down list, and select Ranger for the target cluster.
  3. 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.
  4. Contact O&M personnel and send the collected logs.

Alarm Clearing

After the fault that triggers the alarm is rectified, the alarm is automatically cleared.

Related Information

None

Did you find this page helpful?

Submit successfully!

Thank you for your feedback. Your feedback helps make our documentation better.

Failed to submit the feedback. Please try again later.

Which of the following issues have you encountered?







Please complete at least one feedback item.

Content most length 200 character

Content is empty.

OK Cancel