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.
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
agent/cache: Store leases in-order in persistent cache so that restore respects dependencies #12843
agent/cache: Store leases in-order in persistent cache so that restore respects dependencies #12843
Changes from 9 commits
60daf78
b316b6b
2b74377
1ea9967
a0560ed
6284dbf
19c1b61
1abadcc
b3d25c6
93cc29f
c3893a2
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this mean we need to do the migration once more? Could we end up in a state where a migration will never succeed? If so, perhaps it would make sense to scrap the db and start fresh.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If the migration fails, something super weird has happened because migrations should be very rare (we only explicitly support persistent stores in k8s today) and failures should also be very rare because the schema creation/migration code is very lenient. So I'd prefer that an operator gets a chance to clean up/debug before we wipe everything automatically.