Feature Request: Support Un-equal Workers natively
- Dominant language
- C#
- Stars
- 1.7k
- Forks
- 335
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 6
Description
Assuming that I have an orchestration that consist of 3 tasks - A, B, C. I also have 2 workers (running on different processes/nodes), where worker is a "leader" and the other is a "worker/slave".
I'd like to be able to configure that certain tasks - e.g. Task C in the above example - should be performed only on the "leader" node.
I as able to achieve something like that, in a very inefficient manner - in the "leader" node, I started a Worker that can handle the Orchestration and Task A. In the "worker" node, I started a Worker that can handle the Orchestration and Tasks B & C. This works, because eventually, the "leader" node will retrieve the Task A message from the queue. However, it's very inefficient, since "worker" node has an equal chance of getting a Task A message, and then it will throw an exception, and "return" the message to the queue.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.