Updated on 2022-08-12 GMT+08:00

ALM-44004 Presto Coordinator Resource Group Queuing Tasks Exceed the Threshold

Description

This alarm is generated when the system detects that the number of queuing tasks in a resource group exceeds the threshold. The system queries the number of queuing tasks in a resource group through the JMX interface. You can choose Components > Presto > Service Configuration (switch Basic to All) > Presto > resource-groups to configure a resource group. You can choose Components > Presto > Service Configuration (switch Basic to All) > Coordinator > Customize > resourceGroupAlarm to configure the threshold of each resource group.

Attribute

Alarm ID

Alarm Severity

Auto Clear

44004

Major

Yes

Parameter

Parameter

Description

ServiceName

Service for which the alarm is generated.

RoleName

Role for which the alarm is generated.

HostName

Host for which the alarm is generated.

Impact on the System

If the number of queuing tasks in a resource group exceeds the threshold, a large number of tasks may be in the queuing state. The Presto task time exceeds the expected value. When the number of queuing tasks in a resource group exceeds the maximum number (maxQueued) of queuing tasks in the resource group, new tasks cannot be executed.

Possible Causes

The resource group configuration is improper or too many tasks in the resource group are submitted.

Procedure

  1. Choose Components > Presto > Service Configuration (switch Basic to All) > Presto > resource-groups to adjust the resource group configuration.
  2. You can choose Components > Presto > Service Configuration (switch Basic to All) > Coordinator > Customize > resourceGroupAlarm to modify the threshold of each resource group.
  3. Collect fault information.

    1. Log in to the cluster node based on the host name in the fault information and query the number of queuing tasks based on Resource Group in the additional information on the Presto client.
    2. Log in to the cluster node based on the host name in the fault information, view the /var/log/Bigdata/nodeagent/monitorlog/monitor.log file, and search for resource group information to view the monitoring collection information of the resource group.
    3. Contact the O&M personnel and send the collected logs.

Reference

None