chore(shard-distirbutor): extend info to debug assignment conflicts #7506
+17
−2
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 changed?
Extending the transaction with operation in the else branch to get the state in case the comparison fails
Why?
we need to understand why there is a conflict when we assign the shards but it is not possible because etcd is not showing which is the failing comparison, so we need to be able to understand where the conflict is generated
How did you test it?
unit tests that cover this case actually reported the mismatch
Potential risks
Release notes
Documentation Changes