Description
Description
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Migrated | gitlab-migration | T2580 Restore replication between somerset and dbreplica0.euwest.azure | ||
| Migrated | gitlab-migration | T2581 Upgrade PostgreSQLs to 12.x / 13.x | ||
| Migrated | gitlab-migration | T2582 Upgrade belvedere/main to PostgreSQL 12 |
Event Timeline
Comment Actions
olasd@pergamon:~$ sudo clush -w @swh-workers 'puppet agent --disable "Upgrade of the main database"; cd /etc/systemd/system/multi-user.target.wants; for unit in swh-worker@*; do systemctl disable $unit; done; systemctl stop swh-worker@*'
Comment Actions
Done the pg_upgrade process.
Switched barman over to a new database (moved all settings to swh-12 from swh-11); Restarted archiving to that new barman directory.
Restarted the cluster on port 15433 to perform some maintenance ops before restarting the full load.
- analyzed all tables
- I was doing a full vacuum on the revision table, with a larger maintenance_work_mem, but this is taking a while; I'll probably just restart the cluster on the default port now
Comment Actions
I've stopped the cluster, taken a snapshot of the dataset, and restarted the cluster on its default port.
I'll do T2583 before restarting the workers.
Comment Actions
*ahem* Do not forget to restart the storage backends when doing such an upgrade, lest you end up with a slew of PostgreSQL connection errors when your clients connect again.
Restarted worker01 which seemed to be happy, so all other workers have been restarted.
olasd@pergamon:~$ sudo clush -w @swh-workers 'sleep=$((RANDOM * 60 / 32768)); echo sleeping for $sleep; sleep $sleep; puppet agent --enable && puppet agent -t; puppet_status=$?; if [ $puppet_status -eq 2 ]; then systemctl default; else echo puppet exited with unexpected status code $puppet_status; exit 2; fi'