Help Center > > User Guide> MRS Manager Operation Guide> Alarm Reference (Applicable to MRS 2.x or Earlier)> ALM-43010 Heap Memory Usage of the JDBCServer Process Exceeds the Threshold

ALM-43010 Heap Memory Usage of the JDBCServer Process Exceeds the Threshold

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

Description

The system checks the JDBCServer process status every 30 seconds. The alarm is generated when the heap memory usage of the JDBCServer process exceeds the threshold (90% of the maximum memory).

Attribute

Alarm ID

Alarm Severity

Automatically Cleared

43010

Major

Yes

Parameters

Parameter

Description

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.

Impact on the System

If the available JDBCServer process heap memory is insufficient, a memory overflow occurs and the service breaks down.

Possible Causes

The heap memory of the JDBCServer process is overused or the heap memory is inappropriately allocated.

Procedure

  1. Check the heap memory usage.

    1. Go to the cluster details page and choose Alarms.
    2. Select the alarm whose Alarm ID is 43010 and view the IP address and role name of the instance in Location.
    3. Choose Components > Spark > Instance > JDBCServer (IP address of the instance for which the alarm is generated) > Customize > Heap Memory Statistics of the JDBCServer Process. Click OK to view the heap memory usage.
    4. Check whether the heap memory usage of JDBCServer has reached the threshold (90% of the maximum heap memory).
      • If yes, go to 1.e.
      • If no, go to 2.
    5. Choose Components > Spark > Service Configuration. Set Type to All and choose JDBCServer > Tuning. Increase the value of the SPARK_DRIVER_MEMORY parameter as required.
    6. Check whether the alarm is cleared.
      • If yes, no further action is required.
      • If no, go to 2.

  2. Collect fault information.

    1. On MRS Manager, choose System > Export Log.
    2. Contact the O&M personnel and send the collected logs.

Reference

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