https://prefect.io
Join Slack
Hi, where can I configure Lazarus behaviour? We are getting this error `A Lazarus process attempted ...
# prefect-server
m
Hi, where can I configure Lazarus behaviour? We are getting this error 
A Lazarus process attempted to reschedule this run 3 times without success. Marking as failed.
while we are waiting for nodes to free up
k
What are you trying to do? Increase retries or turn Lazarus off or increase the delay?
m
increase retries and the delay
k
You can for Server, but not Cloud I think. Are you on Server?
m
yes, i’m on server
k
I think delay is hardcoded but the limit is here
This is the hardcode
m
is this where we can override?
can we override it in executor? like some values with “PREFECT_SERVER__” prefix
k
Yeah I think
Copy code
PREFECT__SERVER__LAZARUS__RESURRECTION_ATTEMPT_LIMIT
before you start server
m
what about for delay?
k
You have to change the hardcode before you re-deploy 😐
m
hm i see. Thanks!
i think based on the values.yaml file, we might be able to override it with these env variables? “PREFECT__SERVER__LAZARUS__RESURRECTION_ATTEMPT_LIMIT” and “PREFECT__SERVER___SCHEDULER___SCHEDULER__LOOP___SECONDS”_
k
that’s not lazarus. that is the rate at which new flow runs are scheduled
m
ah ok. Got it. Thanks!
Unfortunately configuring in the config.toml didn’t update the lazarus resurrection attempt limit
it’s still showing default 3
A Lazarus process attempted to reschedule this run 3 times without success. Marking as failed.
this was what i added in the prefect config
Copy code
[services]
    [services.lazarus]
    resurrection_attempt_limit = 20
k
I think config is used for 
prefect server start
but not for helm so you need to edit in the helm side of things?
m
hm i tried both but i’m still getting the same error message and didn’t increase the attempts
14 Views
Open in Slack
PreviousNext
Powered by

Prefect Community

Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.

Powered by