https://prefect.io
Join Slack
Using `prefect agent start --pool hello_a_pool --pool hello_b_pool` only starts `hello_b_pool`.
# ask-community
i
Using 
prefect agent start --pool hello_a_pool --pool hello_b_pool
only starts 
hello_b_pool
.
✅ 1
c
Pools are a worker concept , queues are for agents
So an agent can have several queues but only a single pool
i
All right, thank you. Are you saying we should only start work pools with 
prefect worker
? How should we start all work pools at the same time?
c
Yes - pools did not exist before workers
Agents can connect to a pool only as a backwards compatibility function and implementation
i
Oh, I see. Thank you. So 
prefect worker start --pool hello_a_pool --pool hello_b_pool
will start all the pool at the same time?
n
hi @Isaac - you dont have to "start" a work pool, just the worker. Its nice to think of workers as a subscriber to the work pool, the worker just sits and polls the work pool to see if any work has been submitted to the work pool (via schedule, automation etc) if the worker you 
start
finds a flow run queued up in the work pool, the worker will grab the job infra template from the work pool and submit the work to the execution environment
✅ 1
c
Pools are 1:1
✅ 1
There should be one worker <-> one work pool; one work pool could have many work-queues within it however of varying priority: https://docs.prefect.io/2.11.3/concepts/work-pools/#worker-options
i
All right, I get the concept now. Thank you, @Christopher Boyd @Nate.
🦜 2
Open in Slack
PreviousNext
Powered by

Prefect Community

Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.

Powered by