You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I guess, that healthy=False means, thats containts too many late_runs.
I have self hosted prefect server and prefect worker (name: k8s-worker). I use just one queue (name: default). Time to time Prefect stucks and don't process any new jobs. For last two days have happened each night. When I restart worker and server, prefect slowly starts running jobs.
Do you have any idea, how to debug or get new insights?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
prefect version
helm server & worker version
2024.10.25010258
Queue details
Name: default
Type: Kubernetes
Concurrency Limit: None
prefect work-queue inspect default
I guess, that
healthy=False
means, thats containts too manylate_runs
.I have self hosted prefect server and prefect worker (name: k8s-worker). I use just one queue (name: default). Time to time Prefect stucks and don't process any new jobs. For last two days have happened each night. When I restart worker and server, prefect slowly starts running jobs.
Do you have any idea, how to debug or get new insights?
Beta Was this translation helpful? Give feedback.
All reactions