Help Center > > User Guide> FusionInsight Manager Operation Guide (Applicable to 3.x)> Alarm Reference (Applicable to MRS 3.x)> ALM-29107 Tserver Process Memory Usage Exceeds the Threshold

ALM-29107 Tserver Process Memory Usage Exceeds the Threshold

Updated at: Aug 17, 2021 GMT+08:00

Description

The system checks the Kudu service status every 60 seconds. This alarm is generated when the memory usage of the Kudu Tserver process exceeds the threshold.

This alarm is cleared when the memory usage of the Tserver process becomes normal and the system considers that the Kudu instance service recovers.

Attribute

Alarm ID

Alarm Severity

Auto Clear

29107

Critical

Yes

Parameters

Name

Meaning

Source

Specifies the cluster for which the alarm is generated.

ServiceName

Specifies the name of the service for which the alarm is generated.

RoleName

Specifies the name of the role for which the alarm is generated.

Trigger Condition

Specifies the threshold for triggering the alarm.

Impact on the System

Users cannot use the Kudu service.

Possible Causes

The memory usage of the KuduTserver instance is too high.

Procedure

Handle the Kudu instance exceptions.

  1. On FusionInsight Manager, choose O&M > Alarm. On the displayed page, locate the alarm ALM-29107 Tserver Process Memory Usage Exceeds the Threshold and view the alarm source.
  2. Choose O&M > Alarm > Threshold Configuration > Kudu, find the threshold of the alarm, compare the memory usage of the KuduTserver instance in the cluster with the threshold, and find the node whose memory usage exceeds the threshold.

    Add nodes or reschedule jobs to reduce the memory usage of the Tserver node or change the threshold.

  3. Choose O&M > Alarm and check whether the alarm is cleared.

    • If yes, no further action is required.
    • If no, go to step 4.

Collect the fault information.

  1. On FusionInsight Manager, choose O&M > Log > Download.
  2. In the Service area, select the following nodes of the desired cluster.

    • Kudu

  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 send 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