rethinkdb / rethinkdb/docs

Add more details to the backup article

Open
#921 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
CSS
Stars
118
Forks
161
PR merge metrics
No merged PRs in 30d

Description

From a StackOverflow question:

I read article about backing up data, but some issues is not clear for me:

  • What happens with data, that will be changed after backup process was started?
  • Does backup operation work only on current machine? Or will it collect data from all shards in cluster? > - If only on current, should I start backup process on all servers?
  • Is it slow operation so I should forbid all operation to db while backup in progress?

These are all reasonable questions that should be answered by the article itself.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the backup article and the linked StackOverflow question. Clarify what happens to data changed during backup, whether backups cover all shards or require work on each server, and whether database operations should be restricted; done means the article answers all four questions.

Written by the indexing model from the issue text.

Assessment

Domain
databases, documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.