Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Need node affinity setting
See original GitHub issueWhen running several workers on different nodes, we need to be able to apply key/value properties on nodes that we can set a workflow’s constraint to. We also need a way to put a constraint on workflows to make sure two or more with constraint value of X don’t execute on same node.
Ex 1. Node 1-4 have much faster CPUs, so we set property on the nodes of SPEED=High. Workflow X that needs to always run only on one of those four nodes should have a node affinity rule placed on it where only a node with property SPEED is set to HIGH.
Ex 2. Workflow A, B, and C have activities that are disk or memory intensive and never should run at the same time on the same node.
If no node is available, the workflow can be configured to sit in queue for next available or to cancel/not run.
Issue Analytics
- State:
- Created a year ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@jdevillard gave an awesome demo during yesterday’s community meeting that I think will be able to handle this scenario perfectly. I think we can expect a PR soon 😉
@sfmskywalker it would also be nice to be able to see in the table in the dashboard, what node a workflow executed/excuting on.