ALM-45285 TagSync Heap Memory Usage Exceeds the Threshold

Alarm Description

The system checks the heap memory usage of the TagSync service every 60 seconds. This alarm is generated when the heap memory usage of the TagSync instance exceeds the threshold (95% of the maximum memory) for 10 consecutive times. This alarm is cleared when the heap memory usage is less than the threshold.

Alarm Attributes

Alarm ID	Alarm Severity	Alarm Type	Service Type	Auto Cleared
45285	Major	Quality of service	Ranger	Yes

Alarm Parameters

Type	Parameter	Description
Location Information	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.
Additional Information	Trigger Condition	Specifies the alarm triggering condition.

Impact on the System

The service may break down. TagSync is unavailable for Ranger.

Possible Causes

The heap memory usage of the TagSync instance is high or the heap memory is improperly allocated.

Handling Procedure

On FusionInsight Manager, choose O&M > Alarm > Alarms > ALM-45285 TagSync 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.
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 Heap Memory Usage. Click OK.
Check whether the heap memory used by TagSync reaches the threshold (95% of the maximum heap memory by default).
- If yes, go to 4.
- If no, go to 6.
On FusionInsight Manager, choose Cluster > Services > Ranger > Instance > TagSync > Instance Configuration. Click All Configurations and choose TagSync > System. Increase the value of -Xmx in the GC_OPTS parameter based on the site requirements and save the configuration.

If this alarm is generated, the heap memory configured for TagSync cannot meet the heap memory required by the TagSync process. You are advised to change the -Xmx value of GC_OPTS to twice that of the heap memory used by TagSync. You can change the value based on the actual service scenario. For details about how to check the TagSync heap memory usage, see 2.
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.

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