TimelyDataflow / TimelyDataflow/timely-dataflow
[Docs] Clarify failure modes of multiple workers and clusters
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3.6k
- Forks
- 293
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 4
Description
After reading through the docs I'm a little unclear on what happens should a worker fail (process/thread dies, network partition, etc).
Main concerns:
- Does the library panic?
- If not how can I detect failure?
- Can I still receive partial data from live workers if I partition my data appropriately?
If this is documented and I've simply missed it, I apologize in advance :)
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
The issue names no documentation file, test, or entry point. Start by locating the documentation covering multiple workers and clusters, then determine the documented behavior for process or thread failure, network partitions, failure detection, and partial data. Done means these failure modes and expected recovery or detection behavior are clearly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- distributed-systems, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100