Help Center> MapReduce Service> User Guide> Alarm Reference (Available for MRS 3.x)> ALM-29107 Tserver Process Memory Usage Exceeds the Threshold
Updated on 2024-06-19 GMT+08:00
View PDF

ALM-29107 Tserver Process Memory Usage Exceeds the Threshold

Alarm 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.

Alarm Attributes

Alarm ID

Alarm Severity

Auto Cleared

29107

Critical

Yes

Alarm Parameters

Type

Parameter

Description

Location Information

Source

Specifies the cluster for which the alarm was generated.

ServiceName

Specifies the service for which the alarm was generated.

RoleName

Specifies the role for which the alarm was generated.

HostName

Specifies the host for which the alarm was generated.

Additional Information

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.

Handling Procedure

Handle the Kudu instance exceptions.

  1. On FusionInsight Manager, choose O&M > Alarm > Alarms. On the displayed page, locate alarm ALM-29107 Tserver Process Memory Usage Exceeds the Threshold and view the alarm source.
  2. Choose O&M > Alarm > Thresholds > Kudu. Locate the alarm threshold, 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 4.

Collect fault information.

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

Alarm Clearance

This alarm is automatically cleared after the fault is rectified.

Related Information

None