Information about changefeed error scenarios
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 118
- Forks
- 161
- PR merge metrics
- No merged PRs in 30d
Description
I forgot about this issue opened by @ha1331 on the server tracker: https://github.com/rethinkdb/rethinkdb/issues/4637
Moving it over here now:
I didn't find too much about error handling with changes() from the documentation. Also it might be good idea to explain what conditions should be met for the feeds to keep working and how to handle errors. by conditions I mean you can loose feed if any of the primaries go down or the server you connected goes down.
...
We currently lose a changefeed in the scenarios you mention and also if a tables is rebalanced / reconfigured, if the network connection between two relevant servers in the cluster is lost, or if the network connection between the client and the server is lost.
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 existing documentation for changes() and the referenced server issue, https://github.com/rethinkdb/rethinkdb/issues/4637. Document the listed conditions that can stop a feed and explain how errors should be handled, with coverage matching the observed scenarios in the issue.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100