Help Center/ MapReduce Service/ User Guide/ MRS Cluster O&M/ MRS Cluster Alarm Handling Reference/ ALM-29000 Impala Service Unavailable
Updated on 2024-12-17 GMT+08:00
View PDF
Share

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 ID

Alarm Severity

Auto Cleared

29000

Critical

Yes

Alarm Parameters

Type

Parameter

Description

Location Information

Source

Specifies the cluster for which the alarm was generated.

ServiceName

Specifies the service for which the alarm was generated.

RoleName

Specifies the role for which the alarm was generated.

HostName

Specifies the host for which the alarm was generated.

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&ODBS 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 2.
    • If no, go to 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 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 4.
    • If no, go to 5.

  4. Rectify the fault by following the handling procedure of ALM-16004 Hive Service Unavailable or ALM-25500 KrbServer Service Unavailable. Then, check whether the alarm is cleared.

    • If yes, no further action is required.
    • If no, go to 5.

Check whether the Impala process is normal.

  1. On FusionInsight Manager, choose O&M > Alarm > Alarms. Check whether ALM-12007 Process Fault exists in the alarm list.

    • If yes, go to 6.
    • If no, go to 9.

  2. 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 7.

Check whether there are too many JDBC&ODBS connections.

  1. 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 8.
    • If no, go to 9.

  2. Rectify the fault by following 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 the alarm is cleared.

    • If yes, no further action is required.
    • If no, go to 9.

Collect fault information.

  1. On FusionInsight Manager, choose O&M > Log > Download.
  2. Expand the Service drop-down list, and select Impala for the target cluster.
  3. 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.
  4. 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