tarantool / tarantool/tarantool
Implement bucket recovery fiber
Nobody has claimed this yet.
- Dominant language
- Lua
- Stars
- 3.7k
- Forks
- 419
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 88
Description
It works on a replicaset master and recovers bucket, whose relocation has failed for any reason: network problems, one of nodes denial etc. It is quite trivial. Just checks a bucket state on both sender and receiver and decides where make it active and where garbage. Or do nothing, if a relocation is in progress.
Follows #3986.
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 reading issue #3986 and the bucket relocation and recovery entry points in Tarantool's replicaset implementation. Trace how sender and receiver bucket states are checked, including failed relocation and in-progress cases. Done means the recovery fiber makes the bucket active on the correct node, marks the other copy as garbage, or leaves an ongoing relocation unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua
- Domain
- databases, distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100