hey =] couldn’t find a clear explanation in the docs - what could be a reason for me to get a
task is already running
(for a KubernetesRun)? and then
Finished task run for task with final state: 'Running'
…. (other than that, it seems like the task doesn’t really run.
k
Kevin Kho
09/19/2021, 6:28 PM
Hey @Nadav Nuni, this is weird. Are you on a DaskExecutor?
Kevin Kho
09/19/2021, 6:48 PM
What does the UI show with the state?
n
Nadav Nuni
09/19/2021, 9:31 PM
The UI shows that the flow FAILED since the task seemed to return
None
which shouldn’t happen in any reasonable scenario of the flow (I’m expecting a tuple)
Nadav Nuni
09/19/2021, 9:32 PM
It seems like an OOM is happening, I’m not sure where though:
Nadav Nuni
09/19/2021, 9:33 PM
also, after 10minutes, I’m getting this (the flow status is FAILED long before that, though)
Nadav Nuni
09/19/2021, 9:57 PM
also, we are using a
LocalExecutor
, not really sure what that means :X
Nadav Nuni
09/19/2021, 9:58 PM
@Kevin Kho, thanks for your help 🙂
k
Kevin Kho
09/19/2021, 11:25 PM
Ah that does look like your container is running out of memory.So Prefect has heartbeats which check if your Flow is alive. If the underlying infrastructure crashes and the heartbeats die along with the Flow, the UI may show it as running for a while until the Zombie Killer marks it as failed.
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.