Page MenuHomePhabricator

Superset SQL Lab fails to stop query
Closed, ResolvedPublicBUG REPORT

Description

List of steps to reproduce (step by step, including full links if applicable):

What happens?:

  • Query editor shows that query has been running for multiple days (see screenshots below)
  • Attempts to stop query produce the following error: "Failed at stopping query. 'dBJBh54Pr'"
  • New queries cannot be executed from the query editor

What should have happened instead?:

  • It should be possible to stop the query from running and execute a new query

Software version (if not a Wikimedia wiki), browser information, screenshots, other information, etc:

  • OS: macOS Big Sur Version 11.6
  • Browser: Chrome, Version 94.0.4606.81
  • Screenshots:

Screen Shot 2021-10-12 at 15.47.22.png (172×754 px, 17 KB)

Screen Shot 2021-10-12 at 15.47.01.png (126×866 px, 17 KB)

I'm not certain which team to route this issue to -- please let me know if I've gotten it wrong!

Related Objects

Event Timeline

I just set presto_analytics_hive extra parameter engine_params.connect_args.session_props.query_max_run_time to 55s on production, so everything _should_ time out in production moving forward.

I'm just wondering whether it's worth setting the Cancel query on window unload event option on the presto_analytics_hive database in Superset.

superset query cancel.png (969×654 px, 96 KB)

I understand from the bug report that Attempts to stop query produce the following error: "Failed at stopping query so this might not work, but it might be useful to have this as a default option nonetheless.

cc: @JAllemandou

I am also facing this issue, a query has been running for almost 22 hrs.

Screenshot from 2021-12-01 16-56-47.png (51×363 px, 4 KB)

It doesn't seem to affect queries on other tabs though.

I'm not sure exactly what's going on; I tried logging in as cmacholan on superset staging and was able to stop a query to mysql (I ran select sleep(100) on mysql_staging. Could either of @CMacholan or @KCVelaga_WMF add steps to reproduce the unstoppable query?

@razzi sorry, I missed this ping. I have been using Superset consistently, and I no longer face this issue. I will report back (along with the query) if it happens again. Thank you.

Ok thanks for confirming @KCVelaga_WMF!

@CMacholan I'm going to close this; if you run into it again feel free to reopen.