talh3747 opened a new issue, #31814: URL: https://github.com/apache/superset/issues/31814
### Bug description When a SQL query is running is SQL Lab, it can't be stopped error received is "Failed at stopping query." **How to reproduce the bug** 1. Go to the SQL Lab. 2. Write and run a query. 3. Click on the STOP button. 4. Expect to see error "Failed at stopping query." **Expected results** Query should stop running. **Actual results** Query is still runing, unless I kill it from the Trino itself, and failed at stopping query message poppes up. ### Screenshots/recordings _No response_ ### Superset version 4.1.1 ### Python version 3.10 ### Node version I don't know ### Browser Chrome ### Additional context I am trying to upgrade my current superset cluster from superset 0.0.0-dev to superste 4.1.1, using the official helm-chart, and official superset images. I have a master, celery worker, redis as broker and postgres as my metadata backend. My db engine is Trino and when I try to stop queries all I see is the "Failed at stopping query" error and in the master logs I see the /api/v1/query/stop request is always receiving 422 (unprocessable entity). Also, in the worker logs I don't see that he receives tasks and also no additional logs in the redis instance itself, but they are connected. When I lookup in the dev tools I see in the **stop** event this message - "Could not cancel query". I also tries to use the api myself and stop the query with post request with the generated 'client_id' and the right headers and I got 400 over and over again. Also in the master logs I see that when the query is submitted it says in the logs : "Running query on a celery worker" but again no logs in the worker. When I deleted the worker deployment and used only the master, the query did stop properly. ### Checklist - [x] I have searched Superset docs and Slack and didn't find a solution to my problem. - [x] I have searched the GitHub issue tracker and didn't find a similar bug report. - [x] 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. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
