ALM-43011 Non-Heap Memory Usage of the JDBCServer2x Process Exceeds the Threshold

Description

The system checks the JDBCServer2x Process status every 30 seconds. The alarm is generated when the non-heap memory usage of an JDBCServer2x Process exceeds the threshold (95% of the maximum memory).

In MRS 3.3.0-LTS and later versions, the Spark2x component is renamed Spark, and the role names in the component are also changed. For example, JDBCServer2x is changed to JDBCServer. Refer to the descriptions and operations related to the component name and role names in the document based on your MRS version.

Attribute

Alarm ID	Alarm Severity	Auto Clear
43011	Major	Yes

Parameters

Name	Meaning
Source	Specifies the cluster for which the alarm is generated.
ServiceName	Specifies the service name for which the alarm is generated.
RoleName	Specifies the role name for which the alarm is generated.
HostName	Specifies the object (host ID) for which the alarm is generated.
Trigger Condition	Specifies the threshold triggering the alarm. If the current indicator value exceeds this threshold, the alarm is generated.

Impact on the System

If the available JDBCServer2x Process non-heap memory is insufficient, a memory overflow occurs and the service breaks down.

Possible Causes

The non-heap memory of the JDBCServer2x Process is overused or the non-heap memory is inappropriately allocated.

Procedure

Check non-heap memory usage.

On the FusionInsight Manager portal, choose O&M > Alarm > Alarms and select the alarm whose ID is 43011. Check the RoleName in Location and confirm the IP address of HostName.
On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Spark2x > Instance and click the JDBCServer2x for which the alarm is generated to go to the Dashboard page. Click the drop-down menu in the Chart area and choose Customize > Memory > JDBCServer2x Memory Usage Statistics from the drop-down list box in the upper right corner and click OK, Check whether the used non-heap memory of the JDBCServer2x Process reaches the threshold(default value is 95%) of the maximum non-heap memory specified for JDBCServer2x.
- If yes, go to 3.
- If no, go to 7.
Figure 1 JDBCServer2x Memory Usage Statistics
On the FusionInsight Manager home page, choose Cluster > Name of the desired cluster > Services > Spark2x > Instance. Click JDBCServer2x by which the alarm is reported to go to the Dashboard page, click the drop-down list in the upper right corner of the chart area, choose Customize > Memory > Statistics for the non-heap memory of the JDBCServer2x Process, and click OK. Based on the alarm generation time, check the values of the used non-heap memory of the JDBCServer2x process in the corresponding period and obtain the maximum value.

Figure 2 Statistics for the non-heap memory of the JDBCServer2x Process
On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Spark2x > Configurations, and click All Configurations. Choose JDBCServer2x > Tuning. You can change the value of -XX: MaxMetaspaceSize in spark.driver.extraJavaOptions according to the following rules: Ratio of the JDBCServer2x non-heap memory usage to the Threshold of JDBCServer2x Non-Heap Memory Usage Statistics ( JDBCServer2x) in the alarm period.

On the FusionInsight Manager home page, choose O&M > Alarm > Thresholds > Name of the desired cluster > Spark2x > Memory > JDBCServer2x Non-Heap Memory Usage Statistics (JDBCServer2x) to view Threshold.
Restart all JDBCServer2x instances.
After 10 minutes, check whether the alarm is cleared.
- If yes, no further action is required.
- If no, go to 7.

Collect fault information.

On the FusionInsight Manager portal, choose O&M > Log >Download.
Select Spark2x in the required cluster from the Service.
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.
Contact the O&M personnel and send the collected logs.