forked from docs/doc-exports
Reviewed-by: Hasko, Vladimir <vladimir.hasko@t-systems.com> Co-authored-by: Yang, Tong <yangtong2@huawei.com> Co-committed-by: Yang, Tong <yangtong2@huawei.com>
14 KiB
14 KiB
ALM-26051 Storm Service Unavailable
Description
The system checks the Storm service availability every 30 seconds. This alarm is generated if the Storm service becomes unavailable after all Nimbus nodes in a cluster become abnormal.
This alarm is cleared after the Storm service recovers.
Attribute
Alarm ID |
Alarm Severity |
Auto Clear |
---|---|---|
26051 |
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 Storm service.
- Users cannot run new Storm tasks.
Possible Causes
- The Kerberos component is faulty.
- ZooKeeper is faulty or suspended.
- The active and standby Nimbus nodes in the Storm cluster are abnormal.
Procedure
- Check the Kerberos component status. For clusters without Kerberos authentication, skip this step and go to 2.
- Check the ZooKeeper component status.
- Check the status of the active and standby Nimbus nodes.
- Choose .
- In Role, check whether only one active Nimbus node exists.
- Select the two Nimbus instances and choose . Check whether the restart is successful.
- Log in to MRS Manager again and choose . Check whether the health status of Nimbus 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 .
- Contact technical support engineers for help. For details, see technical support.
Related Information
N/A