Help Center/ MapReduce Service/ User Guide/ MRS Cluster O&M/ MRS Cluster Alarm Handling Reference/ ALM-45290 PolicySync Direct Memory Usage Exceeds the Threshold
Updated on 2024-09-23 GMT+08:00
View PDF
Share

ALM-45290 PolicySync Direct Memory Usage Exceeds the Threshold

Alarm Description

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

Alarm Attributes

Alarm ID

Alarm Severity

Auto Cleared

45290

Major

Yes

Alarm Parameters

Parameter

Description

Source

Specifies the cluster for which the alarm is generated.

ServiceName

Specifies the service for which the alarm is generated.

RoleName

Specifies the role for which the alarm is generated.

HostName

Specifies the host for which the alarm is generated.

Trigger Condition

Specifies the threshold for triggering the alarm.

Impact on the System

Direct memory overflow may cause service breakdown.

Possible Causes

The direct memory of the PolicySync process is overused or the direct memory is inappropriately allocated.

Handling Procedure

Check the direct memory usage.

  1. Log in to FusionInsight Manager and choose O&M > Alarm > Alarms > ALM-45290 PolicySync 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 > PolicySync Direct Memory Usage. Click OK.

    Figure 1 PolicySync Direct Memory Usage

  3. Check whether the direct memory used by the PolicySync reaches the threshold (90% 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 > PolicySync. Click Instance Configuration and then All Configurations, and choose PolicySync > System. Set -XX:MaxDirectMemorySize in the GC_OPTS parameter to a larger value based on site requirements and save the configuration.

    If this alarm is generated, the direct memory configured for PolicySync cannot meet the direct memory required by the PolicySync process. You are advised to check the direct memory usage of PolicySync and change the value of -XX:MaxDirectMemorySize in GC_OPTS to the twice of the direct memory used by PolicySync. You can change the value based on the actual service scenario. Refer to 2 to view the TokenServer direct 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.

      When the service is rebooted, it becomes unavailable and can disrupt business operations. When the instance is rebooted, it cannot be used and any tasks running on the current instance node will fail.

Collect fault information.

  1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
  2. Expand the Service drop-down list, and select Ranger for the target cluster.
  3. Click the edit icon 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 provide the collected logs.

Alarm Clearance

This alarm is automatically cleared after the fault is rectified.

Related Information

None.