Change Details

db1083, acting as s1 primary master is on the list of hosts that might have a BBU crash anytime (T258386), also we need to update the kernel (T273280) We need to promote db1163 instead as a primary master. When: 28th April at 05:00 AM UTC Checklist: [x] Double check db1163 has `report_host` enabled T271106 [x] Create a task to communicate the chosen date and send an announcement to the community: T279505 NEW master: db1163 OLD master: db1083 [x] Check configuration differences between new and old master ` pt-config-diff h=db1083.eqiad.wmnet,F=/root/.my.cnf h=db1163.eqiad.wmnet,F=/root/.my.cnf ` [x] Silence alerts on all hosts [x] Set NEW master with weight 0 s1 `dbctl instance db1163 edit` `dbctl config commit -m "Set db1163 with weight 0 T278214"` [x] Topology changes, connect everything to db1163 `db-switchover --timeout=15 --only-slave-move db1083.eqiad.wmnet db1163.eqiad.wmnet` [x] Disable puppet @db1163 and @db1083 ` puppet agent --disable "switchover to db1163"` [x] Merge gerrit puppet change to promote db1163: https://gerrit.wikimedia.org/r/c/operations/puppet/+/682881/ **Failover:** [x] Start the failover `!log Starting s1 eqiad failover from db1083 to db1163 - T278214` [x] Read only on s1 `dbctl --scope eqiad section s1 ro "Maintenance till 06:15M UTC " && dbctl config commit -m "Set s1 as read-only for maintenance T278214"` [x] Check s1 is indeed on read only [x] run switchover script from cumin1001: `db-switchover --skip-slave-move db1083 db1163 ; echo db1083; mysql.py -hdb1083 -e "show slave status\G" ; echo db1163 ; mysql.py -hdb1163 -e "show slave status\G"` [x] Promote db1163 as new master and remove read-only `dbctl --scope eqiad section s1 set-master db1163 && dbctl --scope eqiad section s1 rw && dbctl config commit -m "Promote db1163 to s1 master and remove read-only from s1 T278214"` [x] Restart puppet on old and new masters (for heartbeat): db1163 and db1083 ` run-puppet-agent -e "switchover to db1163"` [x] Apply T276292 and T276150 to db1083 [] Give weight to db1083 in s1 `dbctl instance db1083 edit` **Clean up tasks:** [x] change events for query killer: ``` events_coredb_master.sql on the new master db1163 events_coredb_slave.sql on the new slave db1083 ``` [x] Update DNS: https://gerrit.wikimedia.org/r/c/operations/dns/+/682882/ [x] Update candidate master dbctl notes and pick new candidate master: db1083 ``` dbctl instance db1163 set-candidate-master --section s1 false dbctl instance db1083 set-candidate-master --section s1 true ``` [x] Check tendril was updated [x] Check zarcillo was updated ** Had to be done manually: https://phabricator.wikimedia.org/P13956 [] After 24h: Clone db1118 from db1083 [] Update/resolve phabricator ticket about failover

db1083, acting as s1 primary master is on the list of hosts that might have a BBU crash anytime (T258386), also we need to update the kernel (T273280) We need to promote db1163 instead as a primary master. When: 28th April at 05:00 AM UTC Checklist: [x] Double check db1163 has `report_host` enabled T271106 [x] Create a task to communicate the chosen date and send an announcement to the community: T279505 NEW master: db1163 OLD master: db1083 [x] Check configuration differences between new and old master ` pt-config-diff h=db1083.eqiad.wmnet,F=/root/.my.cnf h=db1163.eqiad.wmnet,F=/root/.my.cnf ` [x] Silence alerts on all hosts [x] Set NEW master with weight 0 s1 `dbctl instance db1163 edit` `dbctl config commit -m "Set db1163 with weight 0 T278214"` [x] Topology changes, connect everything to db1163 `db-switchover --timeout=15 --only-slave-move db1083.eqiad.wmnet db1163.eqiad.wmnet` [x] Disable puppet @db1163 and @db1083 ` puppet agent --disable "switchover to db1163"` [x] Merge gerrit puppet change to promote db1163: https://gerrit.wikimedia.org/r/c/operations/puppet/+/682881/ **Failover:** [x] Start the failover `!log Starting s1 eqiad failover from db1083 to db1163 - T278214` [x] Read only on s1 `dbctl --scope eqiad section s1 ro "Maintenance till 06:15M UTC " && dbctl config commit -m "Set s1 as read-only for maintenance T278214"` [x] Check s1 is indeed on read only [x] run switchover script from cumin1001: `db-switchover --skip-slave-move db1083 db1163 ; echo db1083; mysql.py -hdb1083 -e "show slave status\G" ; echo db1163 ; mysql.py -hdb1163 -e "show slave status\G"` [x] Promote db1163 as new master and remove read-only `dbctl --scope eqiad section s1 set-master db1163 && dbctl --scope eqiad section s1 rw && dbctl config commit -m "Promote db1163 to s1 master and remove read-only from s1 T278214"` [x] Restart puppet on old and new masters (for heartbeat): db1163 and db1083 ` run-puppet-agent -e "switchover to db1163"` [x] Apply T276292 and T276150 to db1083 **Clean up tasks:** [x] change events for query killer: ``` events_coredb_master.sql on the new master db1163 events_coredb_slave.sql on the new slave db1083 ``` [x] Update DNS: https://gerrit.wikimedia.org/r/c/operations/dns/+/682882/ [x] Update candidate master dbctl notes and pick new candidate master: db1083 ``` dbctl instance db1163 set-candidate-master --section s1 false dbctl instance db1083 set-candidate-master --section s1 true ``` [x] Check tendril was updated [x] Check zarcillo was updated ** Had to be done manually: https://phabricator.wikimedia.org/P13956 [] After 24h: Clone db1118 from db1083 [] If needed: give weight to db1083 in s1 `dbctl instance db1083 edit` [] Update/resolve phabricator ticket about failover

db1083, acting as s1 primary master is on the list of hosts that might have a BBU crash anytime (T258386), also we need to update the kernel (T273280) We need to promote db1163 instead as a primary master. When: 28th April at 05:00 AM UTC Checklist: [x] Double check db1163 has `report_host` enabled T271106 [x] Create a task to communicate the chosen date and send an announcement to the community: T279505 NEW master: db1163 OLD master: db1083 [x] Check configuration differences between new and old master ` pt-config-diff h=db1083.eqiad.wmnet,F=/root/.my.cnf h=db1163.eqiad.wmnet,F=/root/.my.cnf ` [x] Silence alerts on all hosts [x] Set NEW master with weight 0 s1 `dbctl instance db1163 edit` `dbctl config commit -m "Set db1163 with weight 0 T278214"` [x] Topology changes, connect everything to db1163 `db-switchover --timeout=15 --only-slave-move db1083.eqiad.wmnet db1163.eqiad.wmnet` [x] Disable puppet @db1163 and @db1083 ` puppet agent --disable "switchover to db1163"` [x] Merge gerrit puppet change to promote db1163: https://gerrit.wikimedia.org/r/c/operations/puppet/+/682881/ **Failover:** [x] Start the failover `!log Starting s1 eqiad failover from db1083 to db1163 - T278214` [x] Read only on s1 `dbctl --scope eqiad section s1 ro "Maintenance till 06:15M UTC " && dbctl config commit -m "Set s1 as read-only for maintenance T278214"` [x] Check s1 is indeed on read only [x] run switchover script from cumin1001: `db-switchover --skip-slave-move db1083 db1163 ; echo db1083; mysql.py -hdb1083 -e "show slave status\G" ; echo db1163 ; mysql.py -hdb1163 -e "show slave status\G"` [x] Promote db1163 as new master and remove read-only `dbctl --scope eqiad section s1 set-master db1163 && dbctl --scope eqiad section s1 rw && dbctl config commit -m "Promote db1163 to s1 master and remove read-only from s1 T278214"` [x] Restart puppet on old and new masters (for heartbeat): db1163 and db1083 ` run-puppet-agent -e "switchover to db1163"` [x] Apply T276292 and T276150 to db1083 [] Give weight to db1083 in s1 `dbctl instance db1083 edit` **Clean up tasks:** [x] change events for query killer: ``` events_coredb_master.sql on the new master db1163 events_coredb_slave.sql on the new slave db1083 ``` [x] Update DNS: https://gerrit.wikimedia.org/r/c/operations/dns/+/682882/ [x] Update candidate master dbctl notes and pick new candidate master: db1083 ``` dbctl instance db1163 set-candidate-master --section s1 false dbctl instance db1083 set-candidate-master --section s1 true ``` [x] Check tendril was updated [x] Check zarcillo was updated ** Had to be done manually: https://phabricator.wikimedia.org/P13956 [] After 24h: Clone db1118 from db1083 [] If needed: give weight to db1083 in s1 `dbctl instance db1083 edit` [] Update/resolve phabricator ticket about failover