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


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


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-15413 GlobalZK Heartbeat Connection Failure

ALM-15413 GlobalZK Heartbeat Connection Failure

Alarm Description

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


Alarm ID

Alarm Severity

Alarm Type



Communications alarm

Alarm Parameters




Specifies the node for which the alarm is reported.


Specifies the ZK check type.


Specifies the service for which the alarm is generated.


Specifies the service for which the alarm is generated.


Specifies the microservice for which the alarm is generated.


Specifies the node for which the alarm is generated.


Specifies the customized alarm information.


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.


  1. Run the following commands to check whether the GlobalZK cluster allows the connection from the client. indicates the IP address of the GlobalZK node and is used as an example in the following commands:

    ./ -server

    ls /

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

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

Alarm Clearing

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

Related Information


Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 45005

Downloads: 33

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