Document failover_sequential_fail_count router option
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 15
- Forks
- 49
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 3
Description
Router's failover constantly pings replicas to know, if they're
alive and properly working. If replica doesn't work correctly,
then its priority is temporary lowered and callro starts to
go to another replica. Moreover, callbro and other requests
skip this replica during balance, if it's unhealthy.
One of the reasons to mark replica as unhealthy is failed
requests in a row. This option allows to specify the number
of such failed requests to mark replica as unhealthy. Note,
that only network problems are considered as failed request.
The option is specified in the root of the config. Default value
is 3.
Requested by @Serpentian in https://github.com/tarantool/vshard/commit/5570d872215686791c2380dd1c8c4f12f7ff68aa.
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 locating the router configuration documentation and reviewing the referenced vshard commit for the option's intended behavior. Document failover_sequential_fail_count, its default of 3, and that only consecutive network failures count toward marking a replica unhealthy.
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
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100