-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
[task scheduling] basic task run queue capacity settings #11825
Conversation
✅ Deploy Preview for prefect-docs-preview ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I had to stare at those tests a while to see if they would cause new flakes but I don't think they will :D
_scheduled_queue: asyncio.Queue | ||
_retry_queue: asyncio.Queue | ||
|
||
@classmethod | ||
async def enqueue(cls, task_run: schemas.core.TaskRun) -> None: | ||
await cls.for_key(task_run.task_key).put(task_run) | ||
|
||
@classmethod | ||
def configure_task_key( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ooo I like that you made it configurable per task-key, that's a great steam valve for users.
adds
to govern max per-task-key queue sizes