[3.5] Set the backend again after recovering v3 backend from snapshot #13501
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
serathius
approved these changes
Nov 25, 2021
hasbro17
pushed a commit
to hasbro17/etcd
that referenced
this pull request
Feb 2, 2022
[3.5] Set the backend again after recovering v3 backend from snapshot
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.
Fix issues/13494.
When etcd recovers v3 backend from a snapshot, then it closes the old backend, see backend.go#L107. So we should set the backend for the consistentIndex again in this case.
This PR is for 3.5. A separate PR pull/13500 has already been submitted for the main branch.
cc @ptabor @serathius @jingyih
/kind bug