Yang, Tong 2195db241c MRS UMN 20231220 version update

Reviewed-by: Pruthi, Vineet <vineet.pruthi@t-systems.com>
Reviewed-by: Rechenburg, Matthias <matthias.rechenburg@t-systems.com>
Co-authored-by: Yang, Tong <yangtong2@huawei.com>
Co-committed-by: Yang, Tong <yangtong2@huawei.com>

2024-05-16 09:40:21 +00:00

7.0 KiB

Raw Permalink Blame History

ALM-45593 IoTDBServer Flush Execution Duration Exceeds the Threshold

Description

This alarm is generated when the data flush duration exceeds the threshold. This alarm is cleared when the flush duration is less than the threshold.

Attribute

Alarm ID	Alarm Severity	Auto Clear
45593	Major	Yes

Parameters

Name	Meaning
Source	Specifies the cluster 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.

Impact on the System

Data write is blocked and the write operation performance is affected.

Possible Causes

The IoTDB flushing on the node is slow. You need to further analyze logs.

Procedure

Collect fault information.

Log in to MRS Manager, choose O&M > Alarm > Alarms. In the real-time alarm list, click in front of this alarm and view the role name and instance IP address in Location.
Choose O&M > Log > Download.
Expand the Service drop-down list, select IoTDB for the target cluster, and click OK.
Expand the Hosts drop-down list. In the Select Host dialog box that is displayed, select the host queried in 1, and click OK.
Click in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time respectively. Then, click Download.
Contact O&M personnel and provide the collected logs.