Document cross-datacenter latency issues
Open
Nobody has claimed this yet.
not_settled
- Dominant language
- CSS
- Stars
- 118
- Forks
- 161
- PR merge metrics
- No merged PRs in 30d
Description
The latency implications of our query model (i.e. masters, automatically hopping to masters if you're querying replicas, and the outdated flag) are not obvious to users (for example, see https://github.com/rethinkdb/rethinkdb/issues/2115).
We should write a document that describes best practices for multi-datacenter setups and goes into detail on latency implications.
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 the query-model details in issue #2115, then review how masters, replicas, and the outdated flag affect multi-datacenter queries. Done means a documentation page explaining latency implications and practical best practices for multi-datacenter setups.
Written by the indexing model from the issue text.
Assessment
- Domain
- databases, distributed-systems, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100