New sharding.rebalancer_bucket_send_timeout configuration option
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 15
- Forks
- 49
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 3
Description
Since: VShard 0.1.41 and Tarantool 3.8.0
The sharding.rebalancer_bucket_send_timeout option sets the timeout
(in seconds) for sending a single bucket during rebalancing. It is
global-scoped. Infinity by default.
Note: Can be used to limit the time, bucket can be unavailable for write
during bucket sending. Can be also used with router.map_callrw request
and with recovery-point-manager role (which uses the map_callrw
under the hood) to guarantee, that the request will succeed. The timeout
for request or role should be > 1.5 * rebalancer_bucket_send_timeout.
Requested by @Serpentian in https://github.com/tarantool/tarantool/commit/9d89284946a804e642250f8bce8821248ca6aedc.
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 from the sharding and rebalancer configuration documentation and search for the sharding.rebalancer_bucket_send_timeout option. Add the stated version, global scope, default, bucket-send behavior, and map_callrw/recovery-point-manager constraint, then verify the wording against the issue and cited Tarantool/VShard context.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100