Document failover_replica_lag_limit router option
Open
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 15
- Forks
- 49
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 3
Description
The maximum number of seconds replica can lag from master.
If upstream.status is sync or follow, then it's lag,
otherwise idle is checked.
The option is specified in the root of the config. Default value
is 30.
Requested by @Serpentian in https://github.com/tarantool/vshard/commit/759635f93ddeb5f40d79ead604770d8263b395e7.
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 with the linked vshard commit and the router configuration documentation. Confirm that failover_replica_lag_limit is a root-level option with a default of 30 seconds, and document the upstream.status cases described in the issue. Done means the option and its lag-checking behavior are clearly documented.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100