Cannot execute query

[mreid-moz]

Issue Summary

When clicking on the "Execute" button for this query, the progress indicator does not appear, and the query execution never appears to complete.

Steps to Reproduce

1. Open the query
2. Click "Execute"
3. See that the button becomes disabled, but the usual progress indicator does not appear.

I expected the "Executing..." UI to appear, with an indication of how long has passed since processing began.

I forked the query here, and it seems to work as expected.

Technical details:

• Redash Version: 4.0.1
• Browser/OS: Firefox Nightly 63 / OSX
• How did you install Redash: This is the redash deployment @ STMO

[jezdez]

Hm, this seems pretty weird, am I'm wondering if this is some kind of permission problem for queries that were created by other users. Definitely worth investigating.

[mars-f]

This has happened to me when I edit my own published queries that have been included on a dashboard.

I tried running a second query that is authored by me, published, and present on the same dashboard, in a different tab in the same Firefox window. That query executed correctly.

Logging in and out again does not fix the issue. I tried a full page refresh to fix the issue before, but that workaround does not appear to be working for me this time. I see no messages in the Javascript console.

Not sure if this helps, but I kept the Firefox page debugger network tab open to observe the buggy query behaviour. When pressing the Execute button on a buggy query page the page sends a single POST to the events endpoint. When pressing the Execute button on a correctly functioning query it has a completely different request/response structure: POST query_results, GET blahblah, POST events, GET blah.

[mars-f]

This is the query where I observed the behaviour.

[alison985]

I can reproduce this on https://sql.telemetry.mozilla.org/queries/56873/source#148629 I did notice that at the bottom where it previously stated a 5 minute runtime clicking the Execute button also changes the text to Running... runtime. I waited 10 minutes to see if it would update but it did not. The POST to events did fire but no others did. In looking at the code path when the Execute button is pressed I don't notice anything on a first pass that may be causing this. The next step is to dig deeper on any nuances of permissioning.

[alison985]

I can't reproduce this locally on the Mozilla fork code. I tried with 2 different user accounts to execute a query created by the 3rd user - one the initial admin account and another brand new account. This makes me think it's not a permissions issue but something else.

[mars-f]

Some more info: this also affects the query when it shows up on dashboards. This query is infected. The query is included in this dashboard. Pressing the Refresh button on the dashboard does not refresh the infected query panels.

[alison985]

I put my detective hat back on today and at least ruled some more things out. @jasonthomas I'm wondering if I can get server logs for the worker and/or redis around the string Inserting job for ee090c3749a4fafbcd914a1ee78c0892?

[jasonthomas]

I looked through the logs and I am not seeing anything in the scheduler or workers that matches ee090c3749a4fafbcd914a1ee78c0892. I tried digging into this more and looks like the execute action is being recorded in the events table for the problematic queries. I am not sure how this translates to scheduling the actual query to run but I assume that the scheduler/workers are not picking up these execute actions for some reason.

[alison985]

Thanks @jasonthomas.

@mreid-moz Are there any other queries this is happening on? I can't reproduce it locally because table doesn't exist on my Athena connection.

[mreid-moz]

I don't have any other examples besides the ones I and mars-f posted here. I've asked on IRC and will update here if I find any more.