No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

HUAWEI CLOUD Stack 6.5.0 Alarm and Event Reference 04

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
ALM-15414 ZooKeeper Heartbeat Connection of the Physical Multi-Tenant Kafka Cluster Is Faulty

ALM-15414 ZooKeeper Heartbeat Connection of the Physical Multi-Tenant Kafka Cluster Is Faulty

Alarm Description

This alarm is reported when the ZooKeeper cluster status fails to be checked.

Attribute

Alarm ID

Alarm Severity

Alarm Type

15414

Major

Communications alarm

Alarm Parameters

Parameter

Description

Node

Specifies the node for which the alarm is reported.

Role

Specifies the ZK check type.

ClusterId

Specifies the ID of the Kafka cluster.

ZkAddr

Specifies the ZooKeeper link address of the Kafka cluster.

CloudService

Specifies the service for which the alarm is generated.

Service

Specifies the service for which the alarm is generated.

MicroService

Specifies the microservice for which the alarm is generated.

NativeMeDn

Specifies the node for which the alarm is generated.

UserDefinedInfo

Specifies the customized alarm information.

solution

Specifies the method for handling the alarm:

Impact on the System

DMS uses GlobalZK to store mapping between topics and clusters and uses ZooKeeper in the sub-clusters to store logs submitted by the Kafka server. If ZooKeeper fails to be connected, the following functions may become unavailable:

  • topic creation
  • topic deletion
  • message consumption
  • message consumption acknowledgement.

Possible Causes

  • The ZooKeeper cluster is faulty.
  • The network connection is interrupted.

Procedure

  1. Run the following commands to check whether the ZooKeeper cluster allows the connection from the client. 192.168.1.1 indicates the IP address of the ZooKeeper node which is used as an example in the following command.

    ./zkCli-start.sh -server 192.168.1.1:32041

    ls /

    • If yes, go to 2.
    • If no, go to 3.

  2. Check whether the network between Ops-check and the ZooKeeper can be pinged.
  3. Contact technical support.

Alarm Clearing

This alarm will be automatically cleared after the fault is rectified.

Related Information

None

Translation
Download
Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 37626

Downloads: 31

Average rating:
This Document Applies to these Products
Related Version
Related Documents
Share
Previous Next