Hi Everyone.
In certain cases our flows are stuck in running state when the k8s pod is deleted or restarted. We have set a high value for terminationGracePeriodSeconds so that the new container created by the k8s pod doesn’t get divested immediately. It stays in terminating state.
We mainly face this issue when a database query is getting executed or the task is interacting with a third party API and the k8s pod gets deleted or restarted then the flow is stuck in running state.
Any idea why this is happening?
k
Kamal
02/06/2024, 4:45 PM
facing same issue, we also set high value for Finished Job TTL, Job Watch Timeout Seconds and Pod Watch Timeout Seconds.....
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.