ClickHouse keeps connecting

[seqwait]

Bug description

ClickHouse keeps connecting, and the api/v1/database/ endpoint remains in a pending state.

The log:

Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/135.0.0.0 Safari/537.36"
2025-05-06 10:25:40,427:DEBUG:superset.models.core:Database._get_sqla_engine(). Masked URL: clickhousedb+connect://root:XXXXXXXXXX@192.168.1.88:18123/default
2025-05-06 10:25:40,475:DEBUG:superset.stats_logger:[stats_logger] (incr) DatabaseRestApi.validate_parameters.success
2025-05-06 10:25:40,475:DEBUG:superset.stats_logger:[stats_logger] (timing) DatabaseRestApi.validate_parameters.time | 197.6319900713861
192.168.1.120 - - [06/May/2025:10:25:40 +0000] "POST /api/v1/database/validate_parameters/ HTTP/1.1" 200 22 "http://192.168.1.88:8088/superset/dashboard/2/?native_filters_key=PWRL-FxDwklK_dEowJYelWodxKGwf9rONiFRWvY6OA_m-OQGKDEMBjOS37nHREQW" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/135.0.0.0 Safari/537.36"
2025-05-06 10:25:40,565:DEBUG:superset.stats_logger:[stats_logger] (incr) test_connection_attempt
2025-05-06 10:25:40,580:DEBUG:superset.models.core:Database._get_sqla_engine(). Masked URL: clickhousedb+connect://root:XXXXXXXXXX@192.168.1.88:18123/default
2025-05-06 10:25:40,625:DEBUG:superset.stats_logger:[stats_logger] (incr) test_connection_success
2025-05-06 10:25:40,766:DEBUG:superset.stats_logger:[stats_logger] (incr) health

Screenshots/recordings

No response

Superset version

master / latest-dev

Python version

3.9

Node version

16

Browser

Chrome

Additional context

No response

Checklist

• I have searched Superset docs and Slack and didn't find a solution to my problem.
• I have searched the GitHub issue tracker and didn't find a similar bug report.
• I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.

[dosubot]

Hello @seqwait! I'm Dosu, a friendly bot here to help you solve bugs, answer questions, and guide you as a contributor while you wait for a human maintainer. Let's tackle that ClickHouse connection issue together!

The issue you're experiencing, where the ClickHouse connection remains in a pending state, could be related to several factors. Here are some potential causes and solutions:

1. Async Query Initialization: The pending state might be due to the initialization of async query jobs, which set the status to STATUS_PENDING initially. This is a normal part of the process before the job starts running or encounters an error ^[1].

2. Timeout Settings: Check the timeout settings for database connections in Superset. You can configure these settings in the Superset configuration file. For example, SQLLAB_TIMEOUT, SUPERSET_TIMEOUT, and SUPERSET_SQLALCHEMY_TIMEOUT are some of the parameters you can adjust to change the timeout duration ^[2].

3. Network Issues: Ensure there are no network issues that might be causing the request to hang. Superset handles network errors by providing specific error messages, such as 'Network error' for failed fetch attempts ^[3].

4. ClickHouse Configuration: Verify that the ClickHouse connection string and parameters are correctly configured. Ensure that the clickhouse-connect library is installed and the connection string is formatted correctly ^[4].

5. Retry Mechanisms: Superset has retry mechanisms for handling failed connection attempts. Ensure that these are functioning correctly and that the system is not stuck in a retry loop ^[5].

If none of these solutions resolve the issue, consider checking the Superset logs for any error messages or stack traces that might provide more insight into the problem.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}