Help Center > > User Guide> FusionInsight Manager Operation Guide> Alarm Reference (Applicable to MRS 3.x)> ALM-29006 Number of ODBC Connections to Impalad Exceeds the Threshold

ALM-29006 Number of ODBC Connections to Impalad Exceeds the Threshold

Updated at: Mar 25, 2021 GMT+08:00

Description

The system checks the number of client connections to the Impalad node every 30 seconds. This alarm is generated when the number of client connections exceeds the customized threshold (60 by default).

This alarm is automatically cleared when the number of client connections is less than the threshold.

Attribute

Alarm ID

Alarm Severity

Automatically Cleared

29006

Major

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.

Trigger Condition

Specifies the threshold for triggering the alarm.

Impact on the System

New client connections may be blocked or even fail.

Possible Causes

The number of client connections maintained by the Impalad service is too large or the threshold is too small.

Procedure

  1. On FusionInsight Manager, choose O&M > Alarm > Thresholds > Impala > Connections > Number of ODBC Connections to Impalad Process (Impalad) to check the threshold.

  2. Check the number of ODBC applications connected to Impalad and stop idle applications. Check whether the alarm is automatically cleared.

    • If yes, no further action is required.
    • If no, go to 3 to change the number of concurrent connections supported by Impalad.

  3. On FusionInsight Manager, choose Cluster > Impala > Configurations > All Configurations > Impalad > Customization. Add the customized parameter --fe_service_threads. The default value of this parameter is 64. Change the value as required and click Save.

  4. After the query tasks on all clients are complete, click the Instance tab. Select all Impalad instances, and restart them.

  5. After the restart is complete, the alarm is cleared. Run the application that uses ODBC to connect to Impalad again.

Alarm Clearing

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

Related Information

None

Did you find this page helpful?

Submit successfully!

Thank you for your feedback. Your feedback helps make our documentation better.

Failed to submit the feedback. Please try again later.

Which of the following issues have you encountered?







Please complete at least one feedback item.

Content most length 200 character

Content is empty.

OK Cancel