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 (2025-07-16)
| Section | Work |
|---|---|
| s5 | Add cl_timestamp_id index to categorylinks table (T399249) (marostegui) |
| Section | Work |
|---|---|
| s5 | Add cl_timestamp_id index to categorylinks table (T399249) (marostegui) |
| s6 | Switchover s6 master (db2214 -> db2229) (T399533) (marostegui) |
| x3 | Switchover x3 master (db2241 -> db2162) (T399456) (marostegui) |
Yesterday (2025-07-15)
| Section | Work |
|---|---|
| es6 | Productionize es2047, es2048, es1047, es1048 (T395771) (marostegui) |
| s5 | Switchover s5 master (db1230 -> db1210) (T399446) (marostegui) |
| s6 | Add cl_timestamp_id index to categorylinks table (T399249) (marostegui) |
| Section | Work |
|---|---|
| s5 | Add cl_timestamp_id index to categorylinks table (T399249) (marostegui) |
Last seven days
| Section | Work |
|---|---|
| es6 | Productionize es2047, es2048, es1047, es1048 (T395771) (marostegui) |
| s5 |
|
| s6 | Add cl_timestamp_id index to categorylinks table (T399249) (marostegui) |
| Section | Work |
|---|---|
| s4 | Switchover s4 master (db2240 -> db2179) (T397163) (fceratto) |
| s5 |
|
| s6 |
|
| x3 | Switchover x3 master (db2241 -> db2162) (T399456) (marostegui) |