Unresponsive quarries cannot be stopped while in running state.
For example, quarry #30241, which used to work properly, is now unresponsive and cannot be stopped. It seems other quarries are unresponsive as well, causing heavy load on server.
Description
Description
Details
Details
Related Changes in Gerrit:
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Use vars.qrun_id when stopping query | analytics/quarry/web | master | +2 -3 |
Related Objects
Related Objects
Event Timeline
Comment Actions
Change 788438 had a related patch set uploaded (by Razzi; author: Razzi):
[analytics/quarry/web@master] Use vars.qrun_id when stopping query
Comment Actions
This bug is a duplicate of T290146. Please mark this one as "duplicate".
It appears there is a much deeper problem. The original quarry and other quarries used to work properly, are now stuck or take forever to execute. It seems like a recent regression.
Comment Actions
Anyone can → Close As Duplicate in the upper right corner. However this task has a proposed patch associated so I wouldn't do that.
Comment Actions
Change 788438 merged by jenkins-bot:
[analytics/quarry/web@master] Use vars.qrun_id when stopping query