Upgrading Foundationdb 7.0.0+

[stefan-kiss (Kiss Stefan)]

With the release of the 7.0.0 (and following versions)

Did the recommended upgrade procedure remain the same ?

• overwrite binaries (or symlink to binaries)
• kill all processes from fdbcli
• wait for fdbmonitor to restart them

Also another question - in regards to multi-region setup - do we also have to atomically restart processes on all the region at the same time or we can stage this operation ?

(example restart process in region 1, then after everything is done restart in second region?

Link to the known procedure below.

Upgrading FoundationDB

You are correct that major/minor releases of FoundationDB are always protocol incompatible, and patch releases are always protocol compatible. This means that rolling upgrades are not an option between major/minor versions. Hopefully I can provide a little bit of insight into why we made this choice. The first consideration is that the master, proxies, resolvers, and transaction logs are a unit in FoundationDB. If any process recruited as any of those roles fail, we recruit all new versions of …

[johscheuer (Johannes Scheuermann)]

The procedure to upgrade your cluster to 7.0.0 or 7.1+ is still the same as before. If you want to upgrade you cluster you should make use of 7.1.6 (or newer) since the older version had a bug in fdbcli kill (revert "kill" command to previous 7.0 behavior by sfc-gh-etschannen · Pull Request #7149 · apple/foundationdb · GitHub) that could lead to some issues during the kill command.

In a multi-region setup you have to upgrade all processes “at once” otherwise the other region is not able to communicate with the upgraded processes.