ALM-43001 Spark2x Service Unavailable

Updated on 2022-08-12 GMT+08:00

View PDF

The system checks the Spark2x service status every 300 seconds. This alarm is generated when the Spark2x service is unavailable.

This alarm is cleared when the Spark2x service recovers.

Alarm ID	Alarm Severity	Auto Clear
43001	Critical	Yes

Name	Meaning
Source	Specifies the cluster for which the alarm is generated.
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.

The tasks submitted by users fail to be executed.

If the alarm is abnormal Spark2x assembly packet, the Spark packet is abnormal. Wait for about 10 minutes. The alarm is automatically cleared.

Check whether service unavailability alarms exist in services depended by Spark2x.

On FusionInsight Manager, choose O&M > Alarm > Alarms.
Check whether the following alarms exist in the alarm list:
- ALM-25500 KrbServer Service Unavailable
- ALM-25000 LdapServer Service Unavailable
- ALM-13000 ZooKeeper Service Unavailable
- ALM-14000 HDFS Service Unavailable
- ALM-18000 Yarn Service Unavailable
- ALM-16004 Hive Service Unavailable
NOTE:

If the multi-instance function is enabled in the cluster and multiple Spark2x service instances are installed, you need to determine the Spark2x service instance where the alarm is generated based on the value of ServiceName in Location. Then you need to check whether the corresponding Hive service is faulty. Spark2x corresponds to Hive, and Spark2x1 corresponds to Hive1. The others follow the same rule.
- If yes, go to 3.
- If no, go to 4.
Handle the service unavailability alarms based on the troubleshooting methods provided in the alarm help.

After all the service unavailability alarms are cleared, wait a few minutes and check whether this alarm is cleared.
- If yes, no further action is required.
- If no, go to 4.

Collect fault information.

On FusionInsight Manager, choose O&M > Log > Download.
Select the following nodes in the required cluster from the Service (Hive is the specific Hive service determined based on ServiceName in the alarm location information).
- KrbServer
- LdapServer
- ZooKeeper
- HDFS
- Yarn
- Hive
Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
Contact the O&M personnel and send the collected logs.

After the fault is rectified, the system automatically clears this alarm.

None

Parent topic: Alarm Reference (Applicable to MRS 3.x)

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.