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

ALM-45287 TagSync Non Heap Memory Usage Exceeds the Threshold

Updated at: Mar 25, 2021 GMT+08:00

Description

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

Attributes

Alarm ID

Alarm Severity

Automatically Cleared

45287

Major

Yes

Parameters

Name

Meaning

Source

Cluster for which the alarm is generated.

ServiceName

Service for which the alarm is generated.

RoleName

Role for which the alarm is generated.

HostName

Host for which the alarm is generated.

Trigger Condition

Threshold for triggering the alarm.

Impact on the System

Non-heap memory overflow may cause service breakdown.

Possible Causes

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

Procedure

Check non-heap memory usage.

  1. On FusionInsight Manager, choose O&M > Alarm > Alarms > ALM-45287 TagSync 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 > TagSync Non Heap Memory Usage. Click OK.
  3. Check whether the non-heap memory used by TagSync 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 > TagSync > Instance Configuration. Click All Configurations and choose TagSync > 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 TagSync instance cannot meet the non-heap memory required by the TagSync process. You are advised to change the -XX:MaxPermSize value of GC_OPTS to the 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.

  1. On FusionInsight Manager, 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 provide 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