ALM-33010 Containers Non-Heap Memory Usage Exceeds the Threshold

Alarm Description

The system checks the non-heap memory usage of WebContainer instances every 30 seconds. This alarm is generated when the non-heap memory usage of a WebContainer instance exceeds the threshold (75%).

This alarm is automatically cleared when the non-heap memory usage is less than or equal to the threshold.

Alarm Attributes

Alarm ID	Alarm Severity	Alarm Type	Service Type	Auto Cleared
33010	Minor	Environment	Containers	Yes

Alarm Parameters

Type	Parameter	Description
Location Information	Source	Specifies the cluster or system 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 threshold for triggering the alarm.

Impact on the System

If the non-heap memory of Containers is insufficient, memory overflow may occur. As a result, the container instance and the BLU deployed in the container are abnormal, and the alarm "The health status of the BLU instance of the Containers service is abnormal" is reported. This alarm is generated when some BLU instances of a BLU role are unhealthy. Service functions are not affected, but the service processing of the BLU may become slow. If all BLU instances of the BLU role are unhealthy, the service corresponding to the BLU cannot provide services.

Possible Causes

The alarm threshold or alarm trigger count is improperly configured.
The memory allocated to the WebContainer instance is improper, or the memory of the BLU deployed on the node leaks. As a result, the usage exceeds the threshold.

Handling Procedure

Check whether the alarm threshold or alarm trigger count is properly configured.

On FusionInsight Manager, choose O&M > Alarm > Alarms, click in the row that contains the alarm, and view the host name and role of the instance for which the alarm is generated in Location.
Choose O&M > Alarm > Thresholds. On the Thresholds page, click the name of the desired cluster, choose Containers > Other > Non_Heap Mem Usage (WebContainer_N), and check whether the trigger count and alarm threshold are set properly for the role for which the alarm is generated.
- If yes, go to 5.
- If no, go to 3.
Change the trigger count and alarm threshold based on the actual non-heap memory usage, and apply the changes.
Wait 2 minutes and check whether the alarm is cleared.
- If yes, no further action is required.
- If no, go to 5.

Check the non-heap memory usage of the WebContainer.

Choose Cluster > Services > Containers > Configurations > All Configurations, choose WebContainer_N(Role) > Default of the role for which the alarm is generated, and check whether the GC_OPTS value is set properly.
- If yes, go to 6.
- If no, go to 7.
Click the Dashboard tab. In the upper right corner, click More and select Restart Service. In the dialog box that is displayed, enter the password to restart the Containers service. Then check whether the alarm is cleared.
- If yes, no further action is required.
- If no, go to 7.

Collect 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 Containers.
Expand the Hosts drop-down list. In the Select Host dialog box that is displayed, select the hosts to which the role belongs, and click OK.
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 personnel and provide the collected logs.