feat: [shard-distributor] rely on dynamic config for migration mode #7391
+92
−25
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?
Move the logic for the migration mode to use dynamic config instead of static config. Next step is to clean up the static config once the behavior is tested with multiple configuration changes.
Why?
migration should be done incrementally and this is easier to control with config rollout and not code rollout.
How did you test it?
unit tests and local development.
Potential risks
shard-distributor-canary service cannot operate correctly if shard-distributor do not use the right configuration
Release notes
Documentation Changes