2020-10-13: Large amount of Sidekiq Queued jobs
Summary
2020-10-13: Large amount of Sidekiq Queued jobs
There have been over 50k background_migration Sidekiq jobs queued for the last 30 minutes.
Timeline
All times UTC.
2020-10-13
-
19:10
- Alert triggered: Large amount of Sidekiq Queued jobs: https://gitlab.pagerduty.com/incidents/PH7A4Z3 -
19:11
- @nnelson declares incident in Slack using/incident declare
command. -
19:35
- @skarbek reaches out -
19:52
- @skarbek indicates that he is pretty convinced that this is a normal background migration operations related to a deployment. -
20:06
- Manually resolved: Large amount of Sidekiq Queued jobs
Click to expand or collapse the Incident Review section.
Incident Review
Summary
- Service(s) affected:
- Team attribution:
- Minutes downtime or degradation:
Metrics
Customer Impact
- Who was impacted by this incident? (i.e. external customers, internal customers)
- What was the customer experience during the incident? (i.e. preventing them from doing X, incorrect display of Y, ...)
- How many customers were affected?
- If a precise customer impact number is unknown, what is the estimated potential impact?
Incident Response Analysis
- How was the event detected?
- How could detection time be improved?
- How did we reach the point where we knew how to mitigate the impact?
- How could time to mitigation be improved?
Post Incident Analysis
- How was the root cause diagnosed?
- How could time to diagnosis be improved?
- Do we have an existing backlog item that would've prevented or greatly reduced the impact of this incident?
- Was this incident triggered by a change (deployment of code or change to infrastructure. If yes, have you linked the issue which represents the change?)?
5 Whys
Lessons Learned
Corrective Actions
Guidelines
Edited by Nels Nelson