- MRS Manager Operation Guide (Applicable to 2.x and Earlier Versions)
- Alarm Reference (Applicable to Versions Earlier Than MRS 3.x)
- ALM-38000 Kafka Service Unavailable
ALM-38000 Kafka Service Unavailable¶
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¶
Check the KrbServer component status. For clusters without Kerberos authentication, skip this step and go to 2.
Go to the MRS cluster details page and click Components.
Note
For MRS 1.7.2 or earlier, log in to MRS Manager and click Services.
Check whether the health status of the KrbServer service is Good.
Rectify the fault by following instructions in ALM-25500 KrbServer Service Unavailable.
Perform 1.b again.
Check the ZooKeeper component status.
Check the Broker status.
Choose Components > Kafka > Broker.
In Role, check whether all instances are normal.
Select all instances of Broker and choose More > Restart Instance.
Choose Components > Kafka. Check whether the health status of Kafka is Good.
Wait 30 seconds and check whether the alarm is cleared.
If yes, no further action is required.
If no, go to 4.
Collect fault information.
On MRS Manager, choose System > Export Log.
Contact technical support engineers for help. For details, see technical support.
Related Information¶
N/A