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

Incidents/2022-03-06 wdqs-categories

From Wikitech-static
< Incidents
Revision as of 17:49, 8 April 2022 by imported>Krinkle (Krinkle moved page Incident documentation/2022-03-06 wdqs-categories to Incidents/2022-03-06 wdqs-categories)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

document status: draft


Incident metadata (see Incident Scorecard)
Incident ID 2022-03-06 wdqs-categories Start 2022-03-06 13:50
Task End 2022-03-06 17:24
People paged sre Responder count 3
Coordinators 0 Affected metrics/SLOs
Impact Sporadic requests were blocked during the time of the incident
Summary The service got overloaded and started to block client traffic, including pybal which ultimately triggered the page. Icinga sent some non-paging alerts at 13:50 but paging alerts didn't get sent until 16:52


  • 13:50 Icinga alerts about CRITICAL - CRITICAL - wdqs-heavy-queries_8888 - none paging
  • 16:52 Icinga notifies about Wikidata Query Service wdqs eqiad - outage starts, paging
  • 16:57 Icinga notifies about Wikidata Query Service wdqs eqiad - paging
  • 17:02 Icinga notifies about Wikidata Query Service wdqs eqiad - paging
  • 17:05 joe restarts wdqs1006
  • 17:07 Icinga notifies about Wikidata Query Service wdqs eqiad - paging
  • 17:07 load on wdqs1006 increases to 120
  • 17:15 jbond tries to reach search team, contacted gehel
  • 17:17 gehel comes online
  • 17:21 jbond restart wdqs services (at gehels request) clusterwide (wdqs::public)
  • 17:24 RECOVERY messages in -operations - outage ends


02:15:05.481 [qtp2137211482-702147] INFO  o.w.q.r.b.t.ThrottlingFilter - A request is being banned. req.requestURI=/bigdata/namespace/wdq/sparql, req.xForwardedFor=, req.queryString=query=%20ASK%7B%20%3Fx%20%3Fy%20%3Fz%20%7D, req.method=GET, req.remoteHost=localhost, req.requestURL=http://localhost/bigdata/namespace/wdq/sparql, req.userAgent=Twisted PageGetter
  • Fix required restarting the wdqs services on the cluster
    sudo cumin -b 1 -s 1 O:wdqs::public 'systemctl restart wdqs-blazegraph wdqs-categories wdqs-updater'



Incident Engagement™ ScoreCard
Rubric Question Score
People Were the people responding to this incident sufficiently different than the previous N incidents? (0/5pt) 3
Were the people who responded prepared enough to respond effectively (0/5pt) 3
Did fewer than 5 people get paged (0/5pt)? 0
Were pages routed to the correct sub-team(s)? 0
Were pages routed to online (working hours) engineers (0/5pt)? (score 0 if people were paged after-hours) 0 (N/A as weekend)
Process Was the incident status section actively updated during the incident? (0/1pt) 0
If this was a major outage noticed by the community, was the public status page updated? If the issue was internal, was the rest of the organization updated with relevant incident statuses? (0/1pt) N/A
Is there a phabricator task for the incident? (0/1pt) 0
Are the documented action items assigned? (0/1pt) 1
Is this a repeat of an earlier incident (-1 per prev occurrence) 0
Is there an open task that would prevent this incident / make mitigation easier if implemented? (0/-1p per task) ?
Tooling Did the people responding have trouble communicating effectively during the incident due to the existing or lack of tooling? (0/5pt) 5
Did existing monitoring notify the initial responders? (1pt) 1
Were all engineering tools required available and in service? (0/5pt) 5
Was there a runbook for all known issues present? (0/5pt) 2
Total score