feat(ha_tracker): Replicadesc implement mergeable interface #10020
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
1bd6fab to
2789864
Compare
e4ac231 to
116b7aa
Compare
4 tasks
dimitarvdimitrov
approved these changes
Dec 2, 2024
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.
What this PR does
In this PR, we implement the
Mergeableinterface forReplicaDescand add tests to verify the implementation. Below, I will describe the high-level algorithm chosen for the Merge function.It’s important to note that the
Mergeableinterface was created with the assumption that the objects implementing it would maintain a "view" (list) of items over which they would iterate. At least based on my understanding after implementing,. In this case, there is only one instance ofReplicaDescfor each key.Merge
We can have 2 possible cases:
In the first case, the incoming Mergeable has the same Replica name as the one already in the KVStore. In this scenario, we keep the one with the most recent timestamp. If the timestamps are the same, we only update if the incoming one has been marked as deleted, in which case we need to make the KVStore aware of the deletion.
In the second case, the incoming Mergeable has a different Replica name. Here, we use the electedAt timestamp to decide which of the two ReplicaDesc objects should be retained.
Which issue(s) this PR fixes or relates to
Fixes #https://github.com/grafana/mimir-squad/issues/2653
Checklist
CHANGELOG.mdupdated - the order of entries should be[CHANGE],[FEATURE],[ENHANCEMENT],[BUGFIX].about-versioning.mdupdated with experimental features.