You are browsing a read-only backup copy of Wikitech. The live site can be found at wikitech.wikimedia.org
Incidents/2022-05-21 - varnish cache busting: Difference between revisions
Jump to navigation
Jump to search
imported>Dzahn (add impact) |
imported>Krinkle No edit summary |
||
| Line 9: | Line 9: | ||
| start = 2022-05-21 19:01:00 | | start = 2022-05-21 19:01:00 | ||
| end = 2022-05-21 19:03:00 | | end = 2022-05-21 19:03:00 | ||
| impact = all users of all wikis, all services behind | | impact = For 3 minutes, outage for all users of all wikis, affecting all services behind CDN layer. | ||
}} | }} | ||
<!-- Reminder: No private information on this page! --> | <!-- Reminder: No private information on this page! --> | ||
A flood of API traffic from an AWS instance caused caching servers to be overloaded. Services behind our caching layer were up, but not reachable during this time. | |||
==Actionables== | ==Actionables== | ||
* | *[[phab:T308952|T308952 - get a legend for haproxy "anomalous session termination states"]] | ||
* | *[[phab:T308940|T308940 - follow-up on user reported ticket with public incident report]] | ||
* | *[[phab:T308941|T308941 - semi related: Klaxon redirects to http]] | ||
==Scorecard== | ==Scorecard== | ||
| Line 94: | Line 94: | ||
| | | | ||
|- | |- | ||
! colspan="2" align="right" |Total score ( | ! colspan="2" align="right" |Total score ('''count of all “yes” answers above)''' | ||
| | | | ||
| | | | ||
|} | |} | ||
Revision as of 21:38, 26 May 2022
document status: draft
Summary
| Incident ID | 2022-05-21 - varnish cache busting | Start | 2022-05-21 19:01:00 |
|---|---|---|---|
| Task | T308940 | End | 2022-05-21 19:03:00 |
| People paged | 5 | Responder count | 7 |
| Coordinators | dzahn | Affected metrics/SLOs | |
| Impact | For 3 minutes, outage for all users of all wikis, affecting all services behind CDN layer. | ||
A flood of API traffic from an AWS instance caused caching servers to be overloaded. Services behind our caching layer were up, but not reachable during this time.
Actionables
- T308952 - get a legend for haproxy "anomalous session termination states"
- T308940 - follow-up on user reported ticket with public incident report
- T308941 - semi related: Klaxon redirects to http
Scorecard
| Question | Answer
(yes/no) |
Notes | |
|---|---|---|---|
| People | Were the people responding to this incident sufficiently different than the previous five incidents? | ||
| Were the people who responded prepared enough to respond effectively | |||
| Were fewer than five people paged? | |||
| Were pages routed to the correct sub-team(s)? | |||
| Were pages routed to online (business hours) engineers? Answer “no” if engineers were paged after business hours. | |||
| Process | Was the incident status section actively updated during the incident? | ||
| Was the public status page updated? | |||
| Is there a phabricator task for the incident? | |||
| Are the documented action items assigned? | |||
| Is this incident sufficiently different from earlier incidents so as not to be a repeat occurrence? | |||
| Tooling | To the best of your knowledge was the open task queue free of any tasks that would have prevented this incident? Answer “no” if there are
open tasks that would prevent this incident or make mitigation easier if implemented. |
||
| Were the people responding able to communicate effectively during the incident with the existing tooling? | |||
| Did existing monitoring notify the initial responders? | |||
| Were all engineering tools required available and in service? | |||
| Was there a runbook for all known issues present? | |||
| Total score (count of all “yes” answers above) | |||