-
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
Prefect job stuck in Pending state #10149
Comments
hi @aivansky-contractor - can you provide more context on when this error arose? are these logs from your agent process? it looks like it could be a transient network error, but hard to tell from the above trace |
Looking into this a bit further, it seems to be an issue with the lower level library we use to handle HTTP/2. This issue reports the symptom and this issue describes the cause. As a temporary measure you can set What happens here is that the server accepts the proposed state transition to Pending, but this exception is raised in the process leading the client to believe the request failed. When the client then retries the request, the server rejects the proposed state transition because the flow run is already in state Pending. |
We believe we are seeing this issue, however we use Google Cloud Run - Push workers Is there anyway to configure a serverless worker to only use HTTP 1 while this ticket is being worked on? |
Quick update - this can be set client side We use
Hopefully string form |
Possibly connected to #11499 |
First check
Bug summary
This is an intermittent issue.
We are suing prefect version 2.10.12 and we are running prefect agent based on docker image 2.10.12-python3.11 deployed into Kubernetes.
We were able to find the following log items associated with jobs stuck in pending.
Reproduction
Error
Versions
Additional context
No response
The text was updated successfully, but these errors were encountered: