Document: How to enable auto-respawning of the RethinkDB service
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 118
- Forks
- 161
- PR merge metrics
- No merged PRs in 30d
Description
A couple of users have asked for an option to automatically restart the RethinkDB service in case it runs out of memory (https://github.com/rethinkdb/rethinkdb/issues/2327).
Once we ship https://github.com/rethinkdb/rethinkdb/issues/2014 and https://github.com/rethinkdb/rethinkdb/issues/2037, it will be possible to achieve this by adding a simple configuration option to the systemd/upstart service configuration (see https://github.com/rethinkdb/rethinkdb/issues/2327#issuecomment-58700756). We should document how to do that exactly, once these issues are settled.
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 reviewing issues 2014 and 2037, then the linked issue 2327 and its referenced comment to understand the prerequisite service behavior. Document the exact systemd/upstart configuration needed to automatically respawn RethinkDB when it runs out of memory, once those issues are settled.
Written by the indexing model from the issue text.
Assessment
- Domain
- devops, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100