Hello! Does anyone know the priority that is placed upon flow labels? For example, if we have 2 servers, each with an agent (say agent

A

and agent

B

for simplicity), and we specify that a flow can run on either

A

or

B

, how is an agent selected to execute the flow run?

It’s whatever agent picks it up first. They poll every 10 seconds so it’s whatever hits it. There is no concept of priority.

Correct, just 2 local agents on distinct servers

Yeah that’s right there is no concept of load balancing

Hmm. Alright. Thanks for the quick clarification! I was kinda hoping for something like it runs on

A

if

A

is available and then falls back on

B

only when necessary - is there some way to accomplish that with the current state of 1.0?

If you send it to A and then A can’t launch it because of a lack of resources, there are services that will requeue it to launch again, but there it won’t explicitly be directed to A. There is nothing in 2.0 that explicitly supports this because this type of concept is more aligned with Task Queues like Celery where you know the resources of the workers and then allocate the work accordingly. They put work in a queue and then don’t release it until there is space. With orchestrators the concern is about the scheduling of work. Dask though has that ability to function as a queue to a cluster so it’s more about executing that concept as tasks rather than Flows. On the Flow level, there is no resource management concept. Does that make sense? Not ruling out the potential of it happening, but not a high priority roadmap item. Does that make sense?

Sure, fair enough. I appreciate the insight 🙂