Scenario request: Lots of workflows with lots of updates as we kill workers
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 102
- Forks
- 29
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 22
Description
Describe the scenario you'd like
Run <workflow-count> workflows on multiple workers that are sent<update-count>updates,. These updates should do some minor work like an activity. The validation step should incorporate some non trivial amount of delay to emulate a real validator. While sending updates kill workers in a non-graceful way. It is expected that no updates should get dropped and not completed.
The variables can be set based on good numbers that stress the environment.
Contributor guide
No contributing guide indexed for this repository
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 files, tests, or entry points. Start by locating the existing scenario and worker-management entry points in this Go load generator, then define stress values for workflow and update counts. Done means updates perform minor activity work, validation includes meaningful delay, workers can be killed non-gracefully during updates, and no updates are dropped or left incomplete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100