ALM-16048 Tez or Spark Library Path Does Not Exist
Description
The system checks the Tez and Spark library paths every 180 seconds. This alarm is generated when the Tez or Spark library path does not exist.
Attribute
Alarm ID |
Alarm Severity |
Auto Clear |
---|---|---|
16048 |
Critical |
Yes |
Parameters
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. |
Impact on the System
The Hive on Tez and Hive on Spark functions are affected.
Possible Causes
The Tez or Spark library path is deleted from the HDFS.
Procedure
Check the default Hive data warehouse.
- Log in to the node where the client is located as user root.
- Run the following command to check whether the tezlib or sparklib directory exists in the hdfs://hacluster/user/{User name}/.Trash/Current/ director:
hdfs dfs -ls hdfs://hacluster/user/<username>/.Trash/Current/
For example, the following information shows that /user/hive/tezlib/8.1.0.1/ and /user/hive/sparklib/8.1.0.1/ exist.
host01:/opt/Bigdata/client # hdfs dfs -ls hdfs://hacluster/user/test/.Trash/Current/ Found 1 items drwx------ - test hadoop 0 2019-06-17 19:53 hdfs://hacluster/user/test/.Trash/Current/user
- Run the following command to restore tezlib and sparklib.
hdfs dfs -mv hdfs://hacluster/user/<username>/.Trash/Current/user/hive/tezlib/8.1.0.1/tez.tar.gz /user/hive/tezlib/8.1.0.1/tez.tar.gz
- Check whether the alarm is cleared.
- If yes, no further action is required.
- If no, go to 5.
Collect fault information.
- Collect related information in the .Trash/Current/ directory on the client background.
- Contact the O&M personnel and send the collected logs.
Alarm Clearing
After the fault is rectified, the system automatically clears this alarm.
Related Information
None
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot