Help Center/ MapReduce Service/ User Guide/ MRS Cluster O&M/ MRS Cluster Alarm Handling Reference/ ALM-50223 Maximum Memory Required by BE Is Greater Than the Remaining Memory of the Machine
Updated on 2024-09-23 GMT+08:00
View PDF
Share

ALM-50223 Maximum Memory Required by BE Is Greater Than the Remaining Memory of the Machine

Alarm Description

The system checks whether the maximum memory required by BE is greater than the available memory every 30 seconds. This alarm is generated when the value is not 1 (1 indicates that the maximum required memory is less than or equal to the available memory, and 0 indicates that the maximum required memory is greater than the available memory).

This alarm is cleared when the maximum required memory is less than or equal to the available memory.

Alarm Attributes

Alarm ID

Alarm Severity

Auto Cleared

50223

Major

Yes

Alarm Parameters

Parameter

Description

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.

Trigger Condition

Specifies the threshold for triggering the alarm.

Impact on the System

A task may fail to apply for memory when running.

Possible Causes

Too much BE node memory has been occupied by other processes, or the maximum memory set for the BE service is too large.

Handling Procedure

Check whether the maximum memory set for the BE node is proper.

  1. Log in to FusionInsight Manager, choose O&M > Alarm > Thresholds, click the name of the desired cluster, and choose Doris > CPU and Memory > Relationship between the maximum memory size of the BE and the remaining memory size of the machine (BE).
  2. Click the edit button next to Trigger Count, change the number based on site requirements, and click OK.
  3. Click Modify in the Operation column, change the alarm threshold based on site requirements, and click OK.
  4. Wait 2 minutes and check whether the alarm is automatically cleared.

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

  1. Log in to the BE node for which the alarm is generated as user omm, run the top command to check the memory usage of processes, locate the process with high memory usage, and check whether the process belongs to the current service and is running properly.

    • If yes, go to 6.
    • If no, isolate or stop the process, or adjust the memory size, and check whether the memory is released.

  2. Log in to the BE node for which the alarm is generated as user omm and run the free -g command to check the total memory and remaining memory in the system and estimate the memory usage.
  3. On FusionInsight Manager, choose Cluster > Services > Doris > Configurations > All Configurations > BE(Role) > Memory and decrease the value of mem_limit. This parameter specifies the maximum memory allowed for BE. Then save the modification and restart the BE instance.

    During BE instance restart, the tasks running on BE nodes will fail. The tasks on BE nodes that are not restarted are not affected.

  4. After the BE instance is restarted, wait 5 minutes and check whether the alarm is cleared.

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

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 Doris for the target cluster.
  3. 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.
  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.