Is there documentation on how to handle
# spicedb
n
Is there documentation on how to handle migrations in a multi-cluster spicedb deployment? Any other potential gotchas to running a multi-cluster spicedb?
v
when you say multi-cluster, you mean multiple SpiceDB clusters sharing the same underlying database, e.g. a multi-region cockroach?
the answer is it depends. If there is a multi-phase migration that needs to be run, then the clusters need to be coordinated. There are also migrations that are not multiphase, but that once run in tandem, lead to breaking chances in the schema (e.g. migration X creates new index, migration X+1 drops old index)
my recommendation: migrate each cluster one spicedb version at a time
and check if the upgrade you are doing does not contain a multiphase migration
n
What do you mean by coordinated?
v
with coordinated I mean that you can't freely let the clusters upgrade, as one making more progress than the others will potentially impact the clusters with versions behind
so you have to manually move the versions one by one in a coordinated fashion
e.g. the following sequence update cluster 1 to 1.39 update cluster 2 to 1.39 update cluster 1 to 1.40 update cluster 2 to 1.40
6 Views