clear-concurrency-limit clears any concurrency limits from a work queue.set-concurrency-limit sets a concurrency limit on a work queue.When using the prefect work-queue Prefect CLI command to configure a work queue, the following subcommands set concurrency limits: If 3 runs are Running or Pending, polling the queue for work will only result in 2 new runs, even if there are many more available, to ensure that the concurrency limit is not exceeded. Work queue concurrency ¶Įach work queue can optionally restrict concurrent runs of matching flows.įor example, a work queue with a concurrency limit of 5 will only release new work if fewer than 5 matching runs are currently in a Running or Pending state. To delete a work queue through the Prefect CLI, use the prefect work-queue delete command with the work queue name. To resume a work queue through the Prefect CLI, use the prefect work-queue resume command with the work queue name. To pause a work queue through the Prefect CLI, use the prefect work-queue pause command: Agents will not receive any work when polling a paused queue. ┃ Scheduled Star… ┃ Run ID ┃ Name ┃ Deployment ID ┃ $ prefect work-queue preview 'test-queue' -hours 12 The optional -hours flag lets you specify the number of hours to look ahead. Prefect work-queue preview displays scheduled flow runs for a specific work queue by ID for the upcoming hour. $ prefect work-queue inspect 'test-queue' `prefect work-queue inspect ` provides all configuration metadata for a specific work queue by ID.
Your agent will deploy flow runs to the infrastructure specified by the deployment. You must start an agent within an environment that can access or create the infrastructure needed to execute flow runs. Default is the value of PREFECT_API_URL.ĭo not display the startup ASCII art for the agent process. The API URL for the Prefect Orion server.
One or more work queues that the agent will poll. If the agent references a work queue that doesn't exist, it will be created automatically.Ĭonfiguration parameters you can specify when starting an agent include: Option Agent configuration ¶Īgents are configured to pull work from one or more work queues. Each agent process sends a unique ID to the server to help disambiguate themselves and let users know how many agents are active. It is possible for multiple agent processes to be started for a single work queue, or for one agent to pull work from multiple work queues. You must configure an agent with a specific work queue.Īgent processes are lightweight polling services that get scheduled work from a work queue and deploy the corresponding flow runs.
It requires a little more setup, but offers much greater control and flexibility with how deployments are executed. If you're familiar with that model, please take some time to understand the new work queue/agent model. The role of agents has changed from their implementation in Prefect 1.0.
0 kommentar(er)
