ALM-29000 Impala Service Unavailable

Alarm Description

The alarm module checks the Impala service status every 30 seconds. This alarm is generated if the Impala service is abnormal.

This alarm is cleared after the Impala service recovers.

Alarm Attributes

Alarm Parameters

Impact on the System

When the Impala service is abnormal, you cannot perform cluster operations on Impala through FusionInsight Manager. The Impala service functions are unavailable.

Possible Causes

• The Hive service is abnormal.
• The KrbServer service is abnormal.
• The Impala process is abnormal.
• There are too many JDBC or ODBC connections.

Handling Procedure

Check whether the services on which Impala depends are normal.

1. On FusionInsight Manager, choose Cluster > Services to check whether Hive and KrbServer are stopped.
   • If yes, start the stopped services and go to Step 2.
   • If no, go to Step 3.

2. On FusionInsight Manager, choose O&M > Alarm > Alarms. In the alarm list, check whether the Impala Service Unavailable alarm is cleared.
   • If yes, no further action is required.
   • If no, go to Step 3.

3. On FusionInsight Manager, choose O&M > Alarm > Alarms. In the alarm list, check whether ALM-16004 Hive Service Unavailable and ALM-25500 KrbServer Service Unavailable exist.
   • If yes, go to Step 4.
   • If no, go to Step 5.

4. Rectify the fault by following the handling procedure of "ALM-16004 Hive Service Unavailable" and "ALM-25500 KrbServer Service Unavailable". Then, check whether the alarm is cleared.
   • If yes, no further action is required.
   • If no, go to Step 5.

Check whether the Impala process is normal.

5. On FusionInsight Manager, choose O&M > Alarm > Alarms. Check whether ALM-12007 Process Fault exists in the alarm list.
   • If yes, go to Step 6.
   • If no, go to Step 9.

6. Rectify the fault by following the handling procedure of "ALM-12007 Process Fault", and then check whether the alarm is cleared.
   • If yes, no further action is required.
   • If no, go to Step 7.

Check whether there are too many JDBC or ODBC connections.

7. On FusionInsight Manager, choose O&M > Alarm > Alarms. In the alarm list, check whether "ALM-29005 Number of JDBC Connections to Impalad Exceeds the Threshold" or "ALM-29006 Number of ODBC Connections to Impalad Exceeds the Threshold" exists.
   • If yes, go to Step 8.
   • If no, go to Step 9.

8. Rectify the fault by referring to the handling procedure of "ALM-29005 Number of JDBC Connections to Impalad Exceeds the Threshold" or "ALM-29006 Number of ODBC Connections to Impalad Exceeds the Threshold". Then, check whether this alarm is cleared.
   • If yes, no further action is required.
   • If no, go to Step 9.

Collect fault information.

9. On FusionInsight Manager, choose O&M > Log > Download.
10. Expand the Service drop-down list, and select Impala for the target cluster.
11. Click the edit icon in the upper right corner, and set Start Date and End Date for log collection to 1 hour ahead of and after the alarm generation time, respectively. Then, click Download.
12. Contact O&M personnel and provide the collected logs.

Alarm Clearance

After the fault that triggers the alarm is rectified, the alarm is automatically cleared.

Related Information

None