RFC: Support dynamic reconfiguration of "buckets"
Open
Nobody has claimed this yet.
area/API
kind/feature
lifecycle/frozen
- Dominant language
- Go
- Stars
- 276
- Forks
- 344
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
/area API
/kind feature
I mentioned this in slack, but given that we already support being promoted to and demoted from "leader" dynamically, could we support dynamically changing the bucket count by:
- Demoting all the current buckets,
- Promoting new buckets as we gain ownership of them.
I haven't looked deeply into what this would entail at a code level yet, but I wanted to float the idea for broader discussion.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing dynamic leader promotion and demotion behavior, then trace how bucket ownership is assigned and changed. Determine whether demoting current buckets and promoting newly owned buckets preserves the project’s invariants, and document the expected behavior and tests before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100