Closed
Bug 1426332
Opened 7 years ago
Closed 7 years ago
queries not running in FxA re:dash
Categories
(Data Platform and Tools :: General, enhancement)
Data Platform and Tools
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: stomlinson, Unassigned)
Details
Since Dec 15th, FxA re:dash queries have stopped completing. Every time I kick off a query, they run for several hours before I give up. Ryan Kelly has tried killing off a bunch of the stalled queries, but new queries suffer from the same problem, they just hang.
Comment 1•7 years ago
|
||
> Ryan Kelly has tried killing off a bunch of the stalled queries
This does seem to have helped *some*, inasmuch as the scheduled queries for updating our dashboards like [1] seem to have completed. Shane, which query are you trying to run that is still giving problems?
[1] https://sql.telemetry.mozilla.org/queries/1751/source
Flags: needinfo?(stomlinson)
Comment 2•7 years ago
|
||
From the redshift control dashboard, it looks like it's this one:
https://sql.telemetry.mozilla.org/queries/49975
Flags: needinfo?(stomlinson)
Comment 3•7 years ago
|
||
Revisiting this after the break, it looks like there's a bug in the above query which was causing redshift to churn something fierce:
WITH
treat_flow_events AS (
SELECT
...
from flow_events
INNER JOIN flow_metadata on flow_events.flow_id = flow_events.flow_id
That INNER JOIN condition is a tautology, so this was taking the full cartesian product of the two tables, and apparently crushing redshift in the process. I rebooted the cluster to purge the in-flight queries, and things *seem* to be running OK now, so I'm going to tentatively mark this resolved but keep on eye on things over the next few days.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•2 years ago
|
Component: Redash (STMO) → General
You need to log in
before you can comment on or make changes to this bug.
Description
•