dosubot[bot] commented on issue #35085: URL: https://github.com/apache/superset/issues/35085#issuecomment-3274245711
<!-- Answer --> This is a known issue in Superset 4.1.3, especially with Databricks and other slow or non-responsive databases. The root cause is that Superset relies on Python-level timeouts, which do not reliably interrupt native/ODBC driver calls—so if the database or driver hangs, Superset can become unresponsive until the underlying call returns or the process is killed. This is particularly problematic with Databricks, where datasource creation or query execution can get stuck in long loops or blocked calls, making the UI hang or requests time out, even though the operation may eventually succeed after a long delay ([details](https://github.com/apache/superset/issues/33388)). You can try to mitigate this by enabling asynchronous query execution (with Celery), tuning timeouts like `SQLLAB_TIMEOUT`, `SUPERSET_WEBSERVER_TIMEOUT`, and increasing Nginx/Gunicorn timeouts ([config example](https://github.com/apache/superset/issues/33218)). However, these settings do not guarantee protection against hangs caused by unresponsive database drivers. Recent Superset releases (after 4.1.3) have added improvements: - `SQLLAB_QUERY_RESULT_TIMEOUT` lets you set a timeout for fetching query results in SQL Lab ([PR #29959](https://github.com/apache/superset/pull/29959)). - `SQLLAB_PAYLOAD_MAX_MB` limits result payload size to prevent browser hangs with large results ([PR #30522](https://github.com/apache/superset/pull/30522)). These help with some causes of unresponsiveness, but do not fully solve the issue with slow or non-responsive databases at the driver level. If your database/driver supports connection or read timeouts, set those at the driver or connection string level. Otherwise, monitor for future Superset releases with improved handling for these scenarios. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/b137805f-50d7-4725-af61-d8809b6b6d2d?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/b137805f-50d7-4725-af61-d8809b6b6d2d?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/b137805f-50d7-4725-af61-d8809b6b6d2d?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/b137805f-50d7-4725-af61-d8809b6b6d2d?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/b137805f-50d7-4725-af61-d8809b6b6d2d?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/b137805f-50d7-4725-af61-d8809b6b6d2d?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/b137805f-50d7-4725-af61-d8809b6b6d2d?feedback_type=other)</sup> [](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=githu b) [](https://go.dosu.dev/discord-bot) [](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/issues/35085) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org For additional commands, e-mail: notifications-h...@superset.apache.org
