ALM-45442 Too Many Concurrent SQL Statements
Alarm Description
The alarm module checks the number of concurrent ClickHouse requests every 30 seconds. This alarm is generated when the number of concurrent ClickHouse requests exceeds the concurrency threshold configured on the UI.
This alarm is cleared when the system detects that the actual number of concurrent requests is less than concurrency threshold.
Alarm Attributes
Alarm ID |
Alarm Severity |
Auto Cleared |
---|---|---|
45442 |
Major |
Yes |
Alarm Parameters
Parameter |
Description |
---|---|
Source |
Specifies the cluster or system 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
If there are too many concurrent SQL statements, a large number of system resources are consumed. As a result, system response becomes slow.
Possible Causes
The ClickHouse service is overloaded.
Handling Procedure
- Log in to FusionInsight Manager, choose O&M > Alarm > Alarms, and view the role name and the IP address for the hostname in Location.
- Choose Cluster > ClickHouse > Instance, select an instance based on the alarm information. Choose Chart > Concurrency to check whether the actual number of concurrent SQL statements is greater than SQL concurrency threshold.
- Confirm with the user whether a large number of tasks were being executed during the alarming period.
- On FusionInsight Manager, choose O&M and click Alarm > Thresholds in the navigation pane on the left. On the displayed page, click ClickHouse > Concurrency and adjust the threshold, or wait until the task is complete. Check whether the alarm is cleared.
- If yes, no further action is required.
- If no, go to 5.
Collect fault information.
- On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
- Expand the Service drop-down list, and select ClickHouse for the target cluster.
- Expand the Hosts drop-down list. In the Select Host dialog box that is displayed, select the abnormal host, and click OK.
- 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.
- Contact O&M personnel and provide the collected logs.
Alarm Clearance
This alarm is automatically cleared after the fault is rectified.
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