kestra icon indicating copy to clipboard operation
kestra copied to clipboard

Killed task remains active

Open nsteinmetz opened this issue 2 years ago • 2 comments

Expected Behavior

Killed task should be killed and marked as failed

Actual Behaviour

Killed task keeps running

We can see the kill call

kestra-kestra-1  | 2022-07-21 07:09:42,297 INFO  default-nioEventLoopGroup-1-4 io.kestra.webserver.access [Date: 2022-07-21T07:09:42.275975Z] [Duration: 21 ms] [Method: DELETE] [Url: /api/v1/executions/6jOT5hnUvGIfODoyYI1r5f/kill] [Status: 204] [Length: 0] [Ip: 109.190.249.185] [Port: 8080]

but nothing happens, no more logs on kestra side nor on postgres side that could provide more info on this.

Task is active for more than a day now and I have no way to kill it afaik.

Steps To Reproduce

No response

Environment Information

  • Kestra Version: 0.5.0-snapshot - lite mode
  • Operating System (OS / Docker / Kubernetes): docker
  • Java Version (If not docker):

Example flow

No response

nsteinmetz avatar Jul 21 '22 07:07 nsteinmetz

It's the same issue than https://github.com/kestra-io/kestra/issues/309. But for the JDBC executor. When we kill an execution, we ask all the workers to find a task to kill, if no one handle this one, this lead to infinite kill and keep it running. Do you have an easy reproduction?

tchiotludo avatar Jul 26 '22 21:07 tchiotludo

I still have my waitiing to be killed flow for days. Except that I don't really know how to reproduce it. I noticed the issue as the job no longer runs for next occurences of the schedule...

nsteinmetz avatar Jul 26 '22 21:07 nsteinmetz