Help Center/ MapReduce Service/ User Guide/ MRS Cluster O&M/ MRS Cluster Alarm Handling Reference/ ALM-45431 Improper ClickHouse Instance Distribution for Topology Allocation
Updated on 2024-09-23 GMT+08:00

ALM-45431 Improper ClickHouse Instance Distribution for Topology Allocation

Alarm Description

The ClickHouseServer instance distribution does not meet the topology allocation requirements.

Alarm Attributes

Alarm ID

Alarm Severity

Auto Cleared

45431

Critical

No

Alarm Parameters

Parameter

Description

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.

Impact on the System

Some ClickHouseServer instances are unavailable.

Possible Causes

During installation or capacity expansion, the number of instances or allocation mode does not meet the topology requirements.

Handling Procedure

  1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Alarm > Alarms, locate the row that contains the alarm, and analyze the cause based on Location and Additional Information.
  2. Handle the alarm based on the additional alarm information and handling method in the following table.

    Additional Information

    Remarks

    Handling Method

    n ClickHouseServer instances should be added to other AZ.

    This alarm is generated when a single cluster is deployed in cross-AZ DR mode. The ClickHouseServer instance deployment does not meet the cross-AZ DR topology allocation requirements. As a result, some instances cannot work properly.

    1. On FusionInsight Manager, choose Cluster > Services > ClickHouse, click the Instance tab, locate the row that contains the alarm, view the host name in Location, and find the AZ for which the alarm is generated in the AZ column based on the host name.
    2. On the Instance page, click Add Instance to add n ClickHouseServer instances to other AZs except the AZ where the alarm is generated.

    n ClickHouseServer instances should be added.

    This alarm is generated when a non-single-cluster is deployed in the default deployment mode of cross-AZ DR. The number of ClickHouseServer instances in the cluster is less than an even number. As a result, some instances cannot work properly.

    1. Determine the number (n) of ClickHouseServer instances to be added based on the alarm information.
    2. On FusionInsight Manager, choose Cluster > Services > ClickHouse, click the Instance tab, and add n ClickHouseServer instances to the cluster.

Alarm Clearance

This alarm needs to be manually cleared after the fault is rectified.

Related Information

None