Proposed as partial solution to parent by @daniel; splitting out for specific follow-up.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | PRODUCTION ERROR | CDanis | T234450 Special:Contributions requests with a high &limit= caused excessive database load | ||
| Declined | None | T250527 Consider enabling max_statement_time on all production DB servers to limit impact of bad queries |
Event Timeline
Comment Actions
There is nothing server-side that needs enablement, this needs implementation on the MW (or any other abstraction layer).
wikiuser@db1089(enwiki)> SET STATEMENT max_statement_time=1 FOR select count(*) from revision; ERROR 1969 (70100): Query execution was interrupted (max_statement_time exceeded) wikiuser@db1089(enwiki)>
wikiadmin@10.64.32.115(enwiki)> SET STATEMENT max_statement_time=1 FOR select count(*) from revision; ERROR 1969 (70100): Query execution was interrupted (max_statement_time exceeded) wikiadmin@10.64.32.115(enwiki)>