ALM-12028 The number of processes that are in the D state on the host exceeds the threshold

Description

The system periodically checks the number of D state processes of user omm on the host every 30 seconds and compares the number with the threshold. The number of host D state processes has a default threshold, and this alarm is generated when the number of processes exceeds the specified threshold.

When the Trigger Count is 1, this alarm is cleared when the number is less than or equal to the threshold. When the Trigger Count is greater than 1, this alarm is cleared when the number is less than or equal to 90% of the threshold.

Attribute

Alarm ID	Alarm Severity	Auto Clear
12028	Major	Yes

Parameters

Name	Meaning
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 triggering the alarm. If the current indicator value exceeds this threshold, the alarm is generated.

Impact on the System

Excessive system resources are used and the service process responds slowly.

Possible Causes

The host responds slowly to I/O (disk I/O and network I/O) requests and a process is in the D state.

Procedure

Check the process that is in the D state.

In the alarm list on FusionInsight Manager, click in the row where the alarm is located to view the alarm host address in the alarm details.
Log in to the alarm host as user root, and run the su - omm command to switch to user omm.
Run the following command to view the PID of the process of user omm that is in the D state:

ps -elf | grep -v "\[thread_checkio\]" | awk 'NR!=1 {print $2, $3, $4}' | grep omm | awk -F' ' '{print $1, $3}' | grep D | awk '{print $2}'
Check whether no command output is displayed in 3.
- If yes, the service process is running properly and no further action is required, go to 6.
- If no, go to 5.
Switch to user root, Run the reboot command to restart the alarm host. (Restarting the host brings certain risks. Ensure that the service process runs properly after the restart).
Wait for 5 minutes. Check whether the alarm is cleared.
- If yes, no further action is required.
- If no, go to 7.

Collect fault information.

On the FusionInsight Manager portal, choose O&M > Log > Download.
Select OMS from the Service and click OK.
Click in the upper right corner, and set Start Date and End Date for log collection to 1 hour ahead of and after the alarm generation time, respectively. Then, click Download.
Contact the O&M personnel and send the collected log information.