TimelyDataflow / TimelyDataflow/timely-dataflow
Is having the same number of workers in each process necessary?
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3.6k
- Forks
- 293
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 4
Description
I ran the following commands in two separate shells for the "hello" example.
cargo run --example hello -- -w2 -n2 -p0
cargo run --example hello -- -w3 -n2 -p1
And it stops after printing
worker 0: hello 0
worker 1: hello 1
for worker with index 0.
Is this behavior expected and you have some assumption of having the same number of workers in each process? Otherwise, I can fix it if you point me to the place to start looking for the issue.
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 reproducing the two cargo run commands from the hello example and compare the observed output with the expected behavior. Trace how the example coordinates workers across the two processes, then determine whether equal worker counts are required. Done means the worker-count assumption is confirmed and the behavior is fixed or clearly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100