Do not upgrade another node in your cluster until the Migrates column shows zeroes. Interrupting data migration may cause data loss.
If you are upgrading a large cluster, you may begin upgrading the next server after a delay of 30-60 seconds, without allowing the data migration to complete. This method may not be fully ACID compliant.
Does anyone have any experience with this? What parts of ACID are lost exactly? I assume that it’s only update propagation that is affected, with no data loss (for a large enough cluster).
Our migrations take 2-3 days after a server restart, so we are eyeballing this method.