-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
[BUG] [Remote State] Add cross chain trimming to handle mutliple valid chains having same state #10913
Comments
linuxpi
added
Cluster Manager
Storage
Issues and PRs relating to data and metadata storage
Storage:Remote
v2.12.0
Issues and PRs related to version 2.12.0
and removed
bug
Something isn't working
labels
Oct 25, 2023
28 tasks
Hi, are we on track for this to be released in 2.12 ? |
Removed 2.12 label @soosinha Can you add the correct target release label? |
rwali-aws
added
ClusterManager:RemoteState
and removed
Storage
Issues and PRs relating to data and metadata storage
Storage:Remote
labels
Jun 6, 2024
@rwali-aws This issue is still valid. |
rajiv-kv
moved this from 🆕 New
to Later (6 months plus)
in Cluster Manager Project Board
Oct 10, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Today we fail bootstrap if we find multiple valid chains. But in few of those cases cross chain validation can help resolve the conflict and choose a single valid chain deterministically.
To Reproduce
Steps to reproduce the behavior:
NA
Expected behavior
In case there are multiple valid chains after intra-chain trimming, and all having previousClusterUUID as na , we can use cross chain trimming to resolve to single valid cluster uuid.
We may also need to immediately cleanup all discarded uuids to avoid the discarded chain causing problem in future.
The text was updated successfully, but these errors were encountered: