tarantool / tarantool/migrations
Risk of crash during migration in a emergency cluster
@a1div0 is already working on this.
Since Jun 16, 2022.
- Dominant language
- Lua
- Stars
- 20
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
Description of the risk
Sometimes, for various reasons, the operations team upgrades only part of the cluster. In our practice, a cluster usually consists of two parts. But in theory it can have three or more parts.
When there are different versions of the application on the cluster in different instances, this is, of course, an abnormal state of the cluster. However, it is possible to run the migration on all leaders with the "migrator" role.
What do you need
I would like to have some kind of verification mechanism that would not allow migration to be launched if at least one instance has an inappropriate version of the application.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.