Skip to content

Avoid duplicated tokens when using minimize spread token strategy#7537

Open
alexqyle wants to merge 1 commit into
cortexproject:masterfrom
alexqyle:duplicate-token
Open

Avoid duplicated tokens when using minimize spread token strategy#7537
alexqyle wants to merge 1 commit into
cortexproject:masterfrom
alexqyle:duplicate-token

Conversation

@alexqyle
Copy link
Copy Markdown
Contributor

What this PR does:

When using minimize spread token strategy, there is a chance that multiple ingesters would have duplicated tokens if they are joining the ring around the same time.

The fix here is to pick multiple token candidates with largest distance and pick one to split based on instance name hash to avoid multiple instances got exactly same token.

Which issue(s) this PR fixes:
NA

Checklist

  • Tests updated
  • Documentation added
  • CHANGELOG.md updated - the order of entries should be [CHANGE], [FEATURE], [ENHANCEMENT], [BUGFIX]
  • docs/configuration/v1-guarantees.md updated if this PR introduces experimental flags

Signed-off-by: Alex Le <leqiyue@amazon.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant