cluster/spec: workaround if store IDs are not monotonically assigned #1011
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 problem does this PR solve?
Workaround of tikv/pd#3303
A case of the issue is at: https://asktug.com/t/topic/66779
What is changed and how it works?
When we iterate over the store list, check if any store is marked as "tombstone" state, if not, use it as the final state of the "host:port" store, otherwise use the state from store that has the max ID.
Sorting the slice should be not necessary as we are iterating the whole list anyway, and are only finding specific item in.
Check List
Tests
Code changes
Side effects
Related changes
Release notes: