-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Zombie Tasks Runs caused by increasing concurrency limit during task run #7203
Comments
@anticorrelator is it possible this is a regression in the new concurrency limit implementation? @j-tr have you encountered this in the open source version? |
That update isn't live yet, but will be soon--I think this error seems consistent with a previous issue that I believe we're fixing with the upcoming release |
Still seeing some runs listed as active. Same code as above:
|
This issue is stale because it has been open 30 days with no activity. To keep this issue open remove stale label or comment. |
This issue was closed because it has been stale for 14 days with no activity. If this issue is important or you have more to add feel free to re-open it. |
First check
Bug summary
when increasing the task concurrency limit while a flow is executing (this would be very useful when having long running flows and a dynamically scaleable db), the number of "Active Tasks Runs" doesn't return to zero after all flows are completed. instead a certain number of tasks is still listed as active by the prefect concurrency-limit inspect command but is in fact in status completed.
Reproduction
Error
Versions
Additional context
relates to #5995
The text was updated successfully, but these errors were encountered: