Upgrade to 17.0 - tentative date 2024-06-03 and 2024-06-04
A new major gitlab version is here, and as usual, that means we have to bump postgresql too. And that means downtime:
-
stop all webservice/gitaly/shell/etc... -
fresh backup of the db -
change postgresql version -
restore backup -
restart everything
But this year, they allow us the possibility to split the db in 2.
In short: we can split the main part and the ci part of the db on 2 different postgres server. The known limitations are not an issue:
- Once data is migrated to the ci database, you cannot migrate it back.
- Significant downtime is expected for larger installations (database sizes of more 100 GB).
But given that our db is 90% CI, this split should hopefully speed up the instance quite a bit by having normal operations handled on a much smaller db.
Thus I think instead of the usual 24h down window, we should prepare a 48h downtime, in case something unexpected happens.