Skip to content

Conversation

@eleonoradgr
Copy link
Contributor

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

Comment on lines +74 to +75
- value: "onboarded"
- value: "local_pass"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is something missing here?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it is the default value, if you don't express contrains, anf then values with constrains for certain namespaces

// KeyName: shardDistributor.migrationMode
// Value type: String
// Default value: local_pass
// Default value: onboarded
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe a comment on diifferent values could be helpful

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it is already there, need to expand up :)

@sankari165
Copy link
Member

nit: there is a typo in the PR title

@eleonoradgr eleonoradgr changed the title feat: [shard-sistributor] rely on dynamic config for migration mode feat: [shard-distributor] rely on dynamic config for migration mode Oct 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants