You are browsing a read-only backup copy of Wikitech. The primary site can be found at

Incident documentation/2021-10-25 s3 db recentchanges replica: Difference between revisions

From Wikitech-static
Jump to navigation Jump to search
(link to phab task)
(3 intermediate revisions by 3 users not shown)
Line 1: Line 1:
{{irdoc|status=draft}} <!--
#REDIRECT [[Incidents/2021-10-25 s3 db recentchanges replica]]
The status field should be one of:
* {{irdoc|status=draft}} - Initial status. When you're happy with the state of your draft, change it to status=review.
* {{irdoc|status=review}} - The incident review working group will contact you then to finalise the report. See also the steps on [[Incident documentation]].
* {{irdoc|status=final}}
== Summary ==
The s3 replica (db1112.eqiad.wmnet) that handles recentchanges/watchlist/contributions queries went down, triggering an icinga alert for the host being down, and a few minutes later an alert for increased appserver latency on GET requests. Confusion over the role of db1112, as it's also the s3 sanitarium master, didn't appropriately recognize the severity. Only while investigating the latency alerts was it realized that the database server was down, leading it to be depooled and restarted via mgmt. Once the host came back, a page was sent out. The incident was resolved by pooling a different s3 replica in its place.
'''Impact''': Average GET latency was up by ~30ms from 18:25 until 19:06. s3 replication to wikireplicas was broken until it was restarted at 2021-10-26 09:15.
* <mark>Todo (Link to relevant source code, graphs, or logs)</mark>
== Actionables ==
* [[phab:T294490|T294490]]: db1112 being down did not trigger any alert that paged until the host was brought back up (we get paged for replication lag but not for host down, Marostegui said for DB hosts we should start paging on HOST down which we normally don't do. This would require a puppet change.)

Latest revision as of 17:49, 8 April 2022