"MySQL server has gone away" during cycle-data on stage and prod

RESOLVED FIXED

Status

Tree Management
Treeherder: Infrastructure
P2
normal
RESOLVED FIXED
3 years ago
3 years ago

People

(Reporter: emorley, Assigned: emorley)

Tracking

(Depends on: 1 bug)

Details

(Assignee)

Comment 1

3 years ago
I ran a manage.py cycle_data manually on stage+prod yesterday, which succeeded, and today's automatic job didn't result in an exceptions on New Relic. Will see how it goes for the next couple of days.

Suspect this may just need bug 1165984 fixing, or else perhaps defragging the artifact tables (bug 1161618) will reduce size on disk enough that the operations against them are quicker.
(Assignee)

Comment 2

3 years ago
> Suspect this may just need bug 1165984 fixing

Bug 1130303, even
Depends on: 1130303
(Assignee)

Updated

3 years ago
Status: NEW → ASSIGNED
(Assignee)

Comment 3

3 years ago
This is still occurring :-(
(Assignee)

Comment 4

3 years ago
Looking at DB node disk usage, cycle-data is still running enough that we're not getting runaway usage, so this can be made a P2.
Priority: P1 → P2
(Assignee)

Updated

3 years ago
Depends on: 1169264
(Assignee)

Comment 5

3 years ago
This seems to have gone away now :-)
Status: ASSIGNED → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.