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 (2026-05-21)

eqiad

Section	Work
es6	Login (T426633) (fceratto)

codfw

Section	Work
pc2	Productionize pc20[21-24] and pc10[21-24] (T418973) (marostegui)

Last seven days

eqiad

Section	Work
es6	Login (T426633) (fceratto)
s5	Switchover s5 master (db1210 -> db1230) (T426087) (fceratto)

codfw

Section	Work
pc1	Productionize pc20[21-24] and pc10[21-24] (T418973) (marostegui)
pc2	Productionize pc20[21-24] and pc10[21-24] (T418973) (marostegui)
pc4	Productionize pc20[21-24] and pc10[21-24] (T418973) (marostegui)
s1	Switchover s1 master (db2212 -> db2203) (T426703) (fceratto)
s4	Drop il_to column from imagelinks table in wmf production (T419635) (fceratto) Switchover s4 master (db2179 -> db2240) (T426590) (fceratto)
s5	Switchover s5 master (db2192 -> db2213) (T426600) (fceratto)
s7	Switchover s7 master (db2218 -> db2220) (T426380) (marostegui)