Hello, I am using prefect==2.6.5 on production with work queues as systemd services. I want to migrate to at least 2.10. Please provide a logical setup for work pool and queues. I don't understand what the pools feature is trying to solve. A tutorial/guidance in the work pool and queue operate together will surely help.

Thank you Bebeto. An upgrade tutorial is in progress. Workers and work pools are typed by the kind of infrastructure. Workers are like smarter agents. The use of work queues changed, as explained below: From the 2.8.0 release notes:

…flow runs can now be prioritized among work queues via work pools! Work pools allow you to organize and prioritize work by grouping related work queues together. Within work pools, you can assign a priority to each queue, and flow runs scheduled on higher priority work queues will be run before flow runs scheduled on lower priority work queues. This allows agents[/workers] to prioritize work that is more important or time-sensitive even if there is a large backlog of flow runs on other work queues in a given work pool.

All existing work queues will be assigned to a default work pool named

default-agent-pool

. Creating a new work pool can be done via the Work Pools page in the UI or via the CLI.

I encourage you to upgrade to 2.10.15 so that you can create work pools with

prefect deploy

and from

prefect.yaml

files. The experience should be much nicer. Any feedback is appreciated. Note that workers and work pools are in beta, but nearing GA. I assume you use agents as systemd services? If so, you could do the same with workers.

Thank, let me try implement that