Document Failure Scenarios/behaviors
- Dominant language
- Go
- Stars
- 610
- Forks
- 63
- Avg merge
- 12h 28m
- Merged PRs (30d)
- 57
Description
What happens to our message delivery and ordering guarantees during various failure scenarios.
Fixed number of failure scenarios:
1. Upstream resource failure
2. Connector Failure / Error - Bug in the connector code. Something about not typical operating behavior.
3. Conduit
4. Transforms
5. Downstream Connector
6. Downstream Resource
Make each one of these steps fail and then write down what the developer can expect.
Resist the urge to fix bad behaviors. We’ll prioritize that work appropriately.
At a minimum get the list of places where we need to test.
Contributor guide
Research direction
No files or tests are named in the issue. Start by locating the message-delivery and ordering entry points, then exercise the six listed failure scenarios: upstream resource, connector, conduit, transforms, downstream connector, and downstream resource. Done means recording developer-visible behavior and listing the places where each scenario needs testing.
Written by the indexing model from the issue text.
Assessment
- Domain
- data-engineering, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100