You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "dosubot[bot] (via GitHub)" <gi...@apache.org> on 2026/05/02 03:02:27 UTC
Re: [D] Query time out in widget , not killing the query executing in database [superset]
GitHub user dosubot[bot] edited a comment on the discussion: Query time out in widget , not killing the query executing in database
<!-- Answer -->
Superset 4.1.2 does not have a configuration to automatically kill or cancel a running database query when a UI timeout occurs. Timeout settings like `SQLLAB_TIMEOUT`, `SUPERSET_WEBSERVER_TIMEOUT`, and `SQLLAB_ASYNC_TIME_LIMIT_SEC` control how long Superset waits for queries or results, but they do not send a kill/cancel request to the database if the UI times out—queries will continue running in the database unless manually stopped by the user (for example, by clicking STOP in SQL Lab) [reference](https://github.com/apache/superset/issues/33218).
Some database engines (Hive, Impala, MySQL, SingleStore) have support for explicit query cancellation, but Superset only triggers these when the user cancels the query, not on timeout [Hive](https://github.com/apache/superset/blob/master/superset/db_engine_specs/hive.py), [Impala](https://github.com/apache/superset/blob/master/superset/db_engine_specs/impala.py), [MySQL](https://github.com/apache/superset/blob/master/superset/db_engine_specs/mysql.py), [SingleStore](https://github.com/apache/superset/blob/master/superset/db_engine_specs/singlestore.py).
If you need queries to be killed after a certain duration, consider enabling asynchronous query execution and setting `SQLLAB_ASYNC_TIME_LIMIT_SEC` to limit how long queries can run before being killed by Celery (in async mode), but this is not tied to UI timeouts [reference](https://github.com/apache/superset/issues/33218). There is currently no built-in way to automatically kill database queries on UI timeout in Superset 4.1.2.
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=reply-with-mention&utm_term=apache%2Fsuperset).*
---
Share context across your team and agents. Try [Dosu](https://dosu.dev?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-tagline&utm_term=apache%2Fsuperset).
[](https://app.dosu.dev/response-feedback?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-feedback&utm_term=apache%2Fsuperset&message_id=fefca4a5-ba2e-4000-aae0-47839e805484) [](https://github.dosu.com/apache/superset?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-learn-repo&utm_term=apache%2Fsuperset) [](https://app.dosu.dev/signup?referrer=openSource&source=github-footer&utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-add-team&utm_term=apache%2Fsuperset)
GitHub link: https://github.com/apache/superset/discussions/35522#discussioncomment-14604396
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org