Add a more pragmatic FAQ on network scenarios
Open
Nobody has claimed this yet.
enhancement
more
- Dominant language
- CSS
- Stars
- 118
- Forks
- 161
- PR merge metrics
- No merged PRs in 30d
Description
Here are some questions that often come up:
- if one runs rethinkdb on multiple nodes, is fault tolerance built in?
- can i read/write to various nodes at the same time?
- is rethinkdb eventually-consistent?
- is multi-datacenter replication supported?
- can insertion/deletion/reads be done on separate nodes?
- can insertion/deletion/reads be done on separate nodes during network partitioning?
- what happens when a master dies? does it automatically pick a new master?
- what happens when the master comes back up?
We already have the answers in http://rethinkdb.com/docs/architecture/, but it takes some reading to get to them. We should have a more straight forward faq/answers to these questions so we don't have to answer them over and over again.
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 network and replication material in the architecture documentation at http://rethinkdb.com/docs/architecture/. Organize the listed network-scenario questions into a concise FAQ using those existing answers. Done means the FAQ addresses each question clearly and reduces the need for repeated explanations.
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
- 35/100