Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Execute Flows Within a Work Queue Based on Priorities #7001

Closed
marvin-robot opened this issue Sep 28, 2022 · 4 comments
Closed

Execute Flows Within a Work Queue Based on Priorities #7001

marvin-robot opened this issue Sep 28, 2022 · 4 comments
Labels
status:stale This may not be relevant anymore

Comments

@marvin-robot
Copy link
Member

Opened from the Prefect Public Slack Community

giorgio.basile4: Hi, I have a question regarding queue priorities. I have a requirement that needs flow runs with "high-priority" to jump all other items in the deployment queue - basically switching from FIFO to LIFO.
I saw the https://docs.prefect.io/concepts/work-queues/#priority-queues|documentation on the topic but I don't think I would be able to support such use case. My understanding is that I would need two "low-priority" and "high-priority" queues, but if there is any item in the high-priority, no "low-priority" flow run should start, and I don't think it can be done easily.
Are priorities within the same queue something that would be supported in the future, or other ways to work it around? Thanks!

khuyen: This is an interesting feature request that could be useful for other users.

I’ll open an issue for this.

<@ULVA73B9P> open “Execute Flows Within a Work Queue Based on Priorities”

Original thread can be found here.

@stratosgear
Copy link

Even better would be some additional API calls that will allow us (after querying a specific work queue for the pending items) to promote or demote then.

Maybe by passing a command like make_first or make_last, or promote (which would make the 3rd item in the queue become 2nd, for example), or demote (well, the 3rd becoming 4th, if not last already).

Our use case is for some long lasting flows, that result in the queue accumulating a considerable amount of pending flows, that the end users would like to rearrange, while they wait for the already executing ones to finish.

That would be extra shinny!

Does this belong here, or should it be a separate issue?

@github-actions
Copy link
Contributor

This issue is stale because it has been open 30 days with no activity. To keep this issue open remove stale label or comment.

@github-actions github-actions bot added the status:stale This may not be relevant anymore label Oct 29, 2022
@zanieb zanieb closed this as completed Mar 20, 2023
@rbarrette
Copy link

rbarrette commented Sep 22, 2023

+1, this is something that would be useful to my team as well, can this be reopened?

@giorgiobasile
Copy link
Contributor

+1, this is something that would be useful to my team as well, can this be reopened?

@rbarrette just seen your comment, priorities are now handled natively in Prefect, checkout the Work Pools & Workers docs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status:stale This may not be relevant anymore
Projects
None yet
Development

No branches or pull requests

5 participants