Better explanation of non-voting replicas and live backup strategy
Open
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 118
- Forks
- 161
- PR merge metrics
- No merged PRs in 30d
Description
What's the recommended ratio of non-voting replicas versus shards + replicas, are they taken into account on tables with "majority" writes, do they give some kind of overhead so I can't delegate non-voting replicas to modest hardware(like cheaper rotational disks), what do I need to change a server tag, etc
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
No documentation file, test, or entry point is identified in the issue. First establish the recommended replica-to-shard ratio, write-consistency behavior, hardware overhead, and server-tag changes, then locate the relevant documentation section and define the completed work as clear guidance covering each question.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100