Mtail stuck on patroni-11
/label incident IncidentActive
Summary
Mtail stuck on patroni-11
Alerted for last WALE backup seen 20 minutes ago, but the actual issue appears to be that mtail on patroni-11 is stuck in a heavy CPU loop and is failing to process new logs. THis is a visibility issue at worse
Timeline
All times UTC.
2020-06-04
- 02:51 - Alert fired for
Last WALE backup was seen 20m 0s ago.
- 03:02 - cmiskell declares incident in Slack using
/incident declare
command. - 03:09 - Killed mtail hard
- 03:11 - Alert cleared
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 Craig Miskell