Closed
Bug 1313219
Opened 8 years ago
Closed 7 years ago
When Query returns 500, Re:Dash continues to say "Query in queue"
Categories
(Cloud Services Graveyard :: Metrics: Pipeline, defect, P1)
Cloud Services Graveyard
Metrics: Pipeline
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: adavis, Assigned: robotblake)
Details
I thought that I had a query taking forever to run but according to Robotblake, the server is returning a 500 with my query but Re:Dash continues to display Query in queue. This means I never get my results and I think the query is still running. Here is the query in question causing this error: https://sql.telemetry.mozilla.org/queries/1522/source
Comment 1•8 years ago
|
||
something you can look at this sprint Blake? let us know if this requires attention from other groups.
Flags: needinfo?(bimsland)
Assignee | ||
Comment 2•8 years ago
|
||
This has to do with bad behavior in the re:dash code, not sure if I'll have time to look into it this sprint, maybe something that :RaFromBRC might be able to look into? I believe [1] and [2] were the (mostly unhelpful) errors that popped up in Sentry when the issue was occurring. [1] https://sentry.prod.mozaws.net/operations/pipeline-sql-prod/issues/341113/ [2] https://sentry.prod.mozaws.net/operations/pipeline-sql-prod/issues/341114/
Flags: needinfo?(bimsland) → needinfo?(rmiller)
Comment 3•8 years ago
|
||
I've opened an issue for this in our re:dash issue tracker: https://github.com/mozilla/redash/issues/12
Flags: needinfo?(rmiller)
Comment 4•8 years ago
|
||
Apparently this has already been resolved upstream: https://github.com/getredash/redash/pull/1121/files Seems like we should assess what else has been done and possibly update our deployment to get this fix.
Assignee | ||
Updated•8 years ago
|
Points: --- → 1
Priority: -- → P1
Assignee | ||
Updated•8 years ago
|
Assignee: nobody → bimsland
Assignee | ||
Comment 5•7 years ago
|
||
This should be taken care of with the most recent release.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Updated•6 years ago
|
Product: Cloud Services → Cloud Services Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•