-
Notifications
You must be signed in to change notification settings - Fork 6.6k
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
Updated backup/restore status when concurrent backups & restores are not allowed #45497
Merged
SmitaRKulkarni
merged 6 commits into
master
from
45486_Fix_flaky_test_for_disallowing_concurrent_backups_restores
Jan 25, 2023
Merged
Updated backup/restore status when concurrent backups & restores are not allowed #45497
SmitaRKulkarni
merged 6 commits into
master
from
45486_Fix_flaky_test_for_disallowing_concurrent_backups_restores
Jan 25, 2023
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
…not allowed Implementation: * Moved concurrent backup/restore check inside try-catch block which sets the status so that other nodes in cluster are aware of failures. * Renamed backup_uuid to restore_uuid in RestoreSettings. Testing: * Updated test test_backup_and_restore_on_cluster/test_disallow_concurrency to check for specific backup/restore id.
… when concurrent backups & restores are not allowed
hanfei1991
approved these changes
Jan 23, 2023
vitlibar
reviewed
Jan 24, 2023
vitlibar
reviewed
Jan 24, 2023
…atus when concurrent backups & restores are not allowed
…rrent_backups_restores
…rrent_backups_restores
vitlibar
reviewed
Jan 24, 2023
vitlibar
approved these changes
Jan 24, 2023
…s/Restores - Updated backup/restore status when concurrent backups & restores are not allowed
vitlibar
approved these changes
Jan 24, 2023
hanfei1991
approved these changes
Jan 24, 2023
Failures are unrelated |
SmitaRKulkarni
deleted the
45486_Fix_flaky_test_for_disallowing_concurrent_backups_restores
branch
January 25, 2023 07:37
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.
Changelog category (leave one):
Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):
Updated backup/restore status when concurrent backups & restores are not allowed resolves #45486
Implementation:
Testing: