release 1.0.0 #72
Merged
release 1.0.0 #72
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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_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.
psergee
approved these changes
Mar 29, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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