feat: change how region id maps to region worker #3384
Merged
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.
I hereby agree to the terms of the GreptimeDB CLA
What's changed and what's your intention?
Change the static region worker mapping method. Remove hashing and use modulo instead.
Hashing mapping is not quite predictable. The new mapping considers table id and region number separately, so regions from one table won't get into the same worker.
This is a workaround and the workload skew problem still exists, and will exist if we don't support mechanisms like work stealing or dynamic mapping.
Checklist
Refer to a related PR or issue link (optional)