I think it makes sense for `TASK_KILLED` to be sent in response to a KILL
call irrespective of the exit status. IIRC, that was the original intention.
On Thu, Sep 21, 2017 at 8:20 PM, Qian Zhang wrote:
> Hi Folks,
>
> I'd like to collect the feedbacks on the task state
Hi Folks,
I'd like to collect the feedbacks on the task state TASK_FINISHED.
Currently the default and command executor will always send TASK_FINISHED
as long as the exit code of task is 0, this cause an issue: when scheduler
initiates a kill task, the executor will send SIGTERM to the task
2 matches
Mail list logo