This release introduces new approach to storing migration state: per-replicaset instead of clusterwide. New approach fixes the issue when new replicaset did not applied the migrations that are already applied on the remaining part of cluster.
To start using 1.0.0 instead of 0.x.x module on existing application, one must first call move_migrations_state through HTTP or Lua API to move current cluster migration state from Cartridge clusterwide configuration to per-replicaset utility spaces. See README.md for upgrade and downgrade scenarios.
Fixed
Migrations do not apply to newly added replica sets in the cluster (gh-65). Applied migration names are moved from the cluster-wide configuration to the space on each node.
Added
An API for moving existing migration names from the cluster configuration to a space.
API for getting applied migrations list for the cluster.
Overview
This release introduces new approach to storing migration state: per-replicaset instead of clusterwide. New approach fixes the issue when new replicaset did not applied the migrations that are already applied on the remaining part of cluster.
To start using 1.0.0 instead of 0.x.x module on existing application, one must first call
move_migrations_statethrough HTTP or Lua API to move current cluster migration state from Cartridge clusterwide configuration to per-replicaset utility spaces. See README.md for upgrade and downgrade scenarios.Fixed
Added