[rebalance] Design reassignment logic for KV tables to prevent unavailability caused by slow KV recovery
- Dominant language
- Java
- Stars
- 2.1k
- Forks
- 625
- Avg merge
- 3d 14h
- Merged PRs (30d)
- 97
Description
### Search before asking
- [x] I searched in the [issues](https://github.com/alibaba/fluss/issues) and found nothing similar.
### Description
Currently, as kv table need to rebuild local snapshot, it will take long time to recovery when leader switch occurred. So this task is aims to design reassignment logic for KV tables to prevent unavailability caused by slow KV recovery
### Willingness to contribute
- [ ] I'm willing to submit a PR!
Contributor guide
No contributing guide indexed for this repository
Research direction
No file, test, or entry point is named. Start by locating the KV-table recovery and rebalance components, then review how leader switches trigger local snapshot recovery. Done means a reviewed reassignment design that addresses slow recovery and prevents KV-table unavailability.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- databases, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100