Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add migrations troubleshoot warning #4629

Merged
merged 1 commit into from
Nov 12, 2024

Conversation

DifferentialOrange
Copy link
Member

Some users expect that --force-reapply or --overwrite will revert the partial result of incorrect migration, yet it is impossible. This patch adds a warning regarding this expectation.

Copy link
Contributor

@p7nov p7nov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please check my suggestions

Comment on lines 52 to 53
Any schema change that was made by incorrect migration before the fail or
cancellation must be resolved manually on each replicaset before reapply.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Any schema change that was made by incorrect migration before the fail or
cancellation must be resolved manually on each replicaset before reapply.
Any schema change that was made by an incorrect migration before its fail or
cancellation must be resolved manually on each replica set before reapply.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated

Comment on lines 54 to 55
Apply flags like ``--force-reapply`` affect only internal migration status and
unable to revert migration scenario itself.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Apply flags like ``--force-reapply`` affect only internal migration status and
unable to revert migration scenario itself.
``--force-reapply`` and other ``tt migrations`` options affect only internal status of the migration
and don't revert changes that it has made in the cluster.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated

@DifferentialOrange DifferentialOrange force-pushed the DifferentialOrange/no-gh-migrations-apply-warn branch from bd9e7b6 to ef162ce Compare November 12, 2024 07:16
Copy link
Contributor

@p7nov p7nov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great, thanks for the addition.

@p7nov p7nov merged commit 6e58edc into latest Nov 12, 2024
1 check passed
@p7nov p7nov deleted the DifferentialOrange/no-gh-migrations-apply-warn branch November 12, 2024 08:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants