When: During a pre-defined DBA maintenance windows
Prerequisites: https://wikitech.wikimedia.org/wiki/MariaDB/Primary_switchover
- Team calendar invite
Affected wikis:: https://noc.wikimedia.org/conf/highlight.php?file=dblists/s3.dblist
Checklist:
NEW primary: db1157
OLD primary: db1223
- Check configuration differences between new and old primary:
sudo pt-config-diff --defaults-file /root/.my.cnf h=db1223.eqiad.wmnet h=db1157.eqiad.wmnet
Failover prep:
- Silence alerts on all hosts:
sudo cookbook sre.hosts.downtime --hours 1 -r "Primary switchover s3 T367140" 'A:db-section-s3'
- Set NEW primary with weight 0
sudo dbctl instance db1157 set-weight 0 sudo dbctl config commit -m "Set db1157 with weight 0 T367140"
- Depool NEW from any specific group (API, vslow, dump) if present.
sudo dbctl instance db1157 edit # If some changes were made: sudo dbctl config commit -m "Remove db1157 from API/vslow/dump T367140"
- Topology changes, move all replicas under NEW primary
sudo db-switchover --timeout=25 --only-slave-move db1223 db1157
- Disable puppet on both nodes
sudo cumin 'db1223* or db1157*' 'disable-puppet "primary switchover T367140"'
- Merge gerrit puppet change to promote NEW primary: https://gerrit.wikimedia.org/r/c/operations/puppet/+/1041363
Failover:
- Log the failover:
!log Starting s3 eqiad failover from db1223 to db1157 - T367140
- Set section read-only:
sudo dbctl --scope eqiad section s3 ro "Maintenance until 06:15 UTC - T367140" sudo dbctl --scope codfw section s3 ro "Maintenance until 06:15 UTC - T367140" sudo dbctl config commit -m "Set s3 eqiad as read-only for maintenance - T367140"
- Check s3 is indeed read-only
- Switch primaries:
sudo db-switchover --skip-slave-move db1223 db1157 echo "===== db1223 (OLD)"; sudo db-mysql db1223 -e 'show slave status\G' echo "===== db1157 (NEW)"; sudo db-mysql db1157 -e 'show slave status\G'
- Promote NEW primary in dbctl, and remove read-only
sudo dbctl --scope eqiad section s3 set-master db1157 sudo dbctl --scope eqiad section s3 rw sudo dbctl --scope codfw section s3 rw sudo dbctl config commit -m "Promote db1157 to s3 primary and set section read-write T367140"
- Restart puppet on both hosts:
sudo cumin 'db1223* or db1157*' 'run-puppet-agent -e "primary switchover T367140"'
Clean up tasks:
- Clean up heartbeat table(s).
sudo db-mysql db1157 heartbeat -e "delete from heartbeat where file like 'db1223%';"
- change events for query killer:
events_coredb_master.sql on the new primary db1157 events_coredb_slave.sql on the new slave db1223
- Update DNS: https://gerrit.wikimedia.org/r/c/operations/dns/+/1041364
- Update candidate primary dbctl and orchestrator notes
sudo dbctl instance db1223 set-candidate-master --section s3 true sudo dbctl instance db1157 set-candidate-master --section s3 false (dborch1001): sudo orchestrator-client -c untag -i db1157 --tag name=candidate (dborch1001): sudo orchestrator-client -c tag -i db1223 --tag name=candidate
- Check zarcillo was updated
- db-switchover should do this. If it fails, do it manually: https://phabricator.wikimedia.org/P13956
sudo db-mysql db1215 zarcillo -e "select * from masters where section = 's3';"
- (If needed): Depool db1223 for maintenance.
sudo dbctl instance db1223 depool sudo dbctl config commit -m "Depool db1223 T367140"
- Change db1223 weight to mimic the previous weight db1157:
sudo dbctl instance db1223 edit
- Update/resolve this ticket.