Help Center/ MapReduce Service/ User Guide/ MRS Manager Operation Guide (Applicable to 2.x and Earlier Versions)/ Alarm Reference (Applicable to MRS 2.x and Earlier Versions)/ ALM-38000 Kafka Service Unavailable (For MRS 2.x or Earlier)
Updated on 2024-04-11 GMT+08:00
View PDF

ALM-38000 Kafka Service Unavailable (For MRS 2.x or Earlier)

Description

The system checks the Kafka service availability every 30 seconds. This alarm is generated if the Kafka service becomes unavailable.

This alarm is cleared after the Kafka service recovers.

Attribute

Alarm ID

Alarm Severity

Auto Clear

38000

Critical

Yes

Parameters

Parameter

Description

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

The cluster cannot provide the Kafka service and users cannot run new Kafka tasks.

Possible Causes

  • The KrbServer component is faulty.
  • The ZooKeeper component is faulty or fails to respond.
  • The Broker node in the Kafka cluster is abnormal.

Procedure

  1. Check the KrbServer component status. For clusters without Kerberos authentication, skip this step and go to 2.

    1. Go to the MRS cluster details page and click Components.
    2. Check whether the health status of the KrbServer service is Good.
      • If yes, go to 2.a.
      • If no, go to 1.c.
    3. Rectify the fault by following instructions in ALM-25500 KrbServer Service Unavailable.
    4. Perform 1.b again.

  2. Check the ZooKeeper component status.

    1. Check whether the health status of the ZooKeeper service is Good.
      • If yes, go to 3.a.
      • If no, go to 2.b.
    2. If the ZooKeeper service is stopped, start it. For other problems, follow the instructions in ALM-13000 ZooKeeper Service Unavailable.
    3. Perform 2.a again.

  3. Check the Broker status.

    1. Choose Components > Kafka > Broker.
    2. In Role, check whether all instances are normal.
      • If yes, go to 3.d.
      • If no, go to 3.c.
    3. Select all instances of Broker and choose More > Restart Instance.
      • If the restart is successful, go to 3.d.
      • If the restart fails, go to 4.
    4. Choose Components > Kafka. Check whether the health status of Kafka is Good.
      • If yes, go to 3.e.
      • If no, go to 4.
    5. Wait 30 seconds and check whether the alarm is cleared.
      • If yes, no further action is required.
      • If no, go to 4.

  4. Collect fault information.

    1. On MRS Manager, choose System > Export Log.
    2. Contact the O&M engineers and send the collected logs.

Related Information

N/A