dragonflydb / dragonflydb/dragonfly
Do blocking only for migrated slots during migration finalization
- Dominant language
- C++
- Stars
- 31.5k
- Forks
- 1.3k
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 137
Description
For now when we do slot migration finalization we block all requests for all slots, using standard PAUSE mechanism until the end of the finalization process. We can improve user experience if we block only requests to the migrated slots.
Contributor guide
Research direction
Locate the slot migration finalization path and the standard PAUSE mechanism, then trace how requests are currently blocked until finalization ends. Determine where migrated slots are identified and verify the behavior for migrated and non-migrated slots. Done means only requests targeting migrated slots are blocked during finalization, while other slots remain available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- databases, distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100