Map of database maintenance

Here you can follow maintenance on our databases. This is useful to spot potential causes for issues in production or avoid interfering with another maintenance work.

A script parses dbctl SAL logs and add entries here. Furthermore, DBAs can add manual entries in this list by logging SAL. It is important that SAL must contain the word "dbmaint", a phabricator ticket id, a section name and name of the datacenter. For example: "!log dbmaint on s2@codfw (T12345)"

Today (2024-12-12)

eqiad

Section	Work
s1	Fix AntiSpoof database schema drifts in production (T381532) (marostegui)

Yesterday (2024-12-11)

codfw

Section	Work
s4	Compile and package MariaDB 10.11.10 and 10.6.20 (T378940) (marostegui)

Last seven days

eqiad

Section	Work
s1	Fix AntiSpoof database schema drifts in production (T381532) (marostegui)
s5	Move db1159 to s5 (T381550) (marostegui)

codfw

Section	Work
s4	Compile and package MariaDB 10.11.10 and 10.6.20 (T378940) (marostegui)
s6	MariaDB Replica SQL: s6 on db2158 is CRITICAL: CRITICAL slave_sql_state Slave_SQL_Running: No, Errno: 1034, Errmsg: Error Index for table recentchanges is corrupt: try to repair it on query. Default database: ruwiki. (T381901) (herron)