mds/quiesce-db: track db epoch separately from the membership epoch#57454
Merged
mds/quiesce-db: track db epoch separately from the membership epoch#57454
Conversation
…a root Signed-off-by: Leonid Usov <leonid.usov@ibm.com>
Tracking the db epoch separately will make sure that replicas only follow leader's epoch choice, even if they are already on the new membership epoch. This eliminates races due to the random order of mdsmap updates. Fixes: https://tracker.ceph.com/issues/65977 Signed-off-by: Leonid Usov <leonid.usov@ibm.com>
Prevent sending of the same version to the same peer more than once a second Signed-off-by: Leonid Usov <leonid.usov@ibm.com>
Contributor
Author
|
@batrick please approve for merge. See #57332 (comment) |
Contributor
Author
|
jenkins test make check |
batrick
approved these changes
May 16, 2024
This was referenced May 27, 2024
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fixes: https://tracker.ceph.com/issues/65977
Tracking the db epoch separately will make sure that replicas only follow leader's epoch choice, even if they are already on the new membership epoch. This eliminates races due to the random order of mdsmap updates.
Show available Jenkins commands
jenkins retest this pleasejenkins test classic perfjenkins test crimson perfjenkins test signedjenkins test make checkjenkins test make check arm64jenkins test submodulesjenkins test dashboardjenkins test dashboard cephadmjenkins test apijenkins test docsjenkins render docsjenkins test ceph-volume alljenkins test ceph-volume toxjenkins test windowsjenkins test rook e2e