You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Bharath Palaksha (Jira)" <ji...@apache.org> on 2019/09/06 04:56:00 UTC
[jira] [Updated] (AIRFLOW-5419) Marking task failed doesn't kill
the task when it is run through impersonation(run_as_user)
[ https://issues.apache.org/jira/browse/AIRFLOW-5419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bharath Palaksha updated AIRFLOW-5419:
--------------------------------------
Description:
Airflow dag which is run using "run_as_user" doesn't get killed when SIGTERM signal is sent to the process.
When task is marked for failure by user or by scheduler - SIGTERM signal is sent to kill the process, but task has a different user id and it requires sudo kill to be killed.
was:
Airflow dag which is run using "run_as_user" doesn't get killed when SIGTERM signal is sent to the process.
When task as marked for failure by user or by scheduler - SIGTERM signal is sent to kill the process, but task has a different user id and it requires sudo kill to be killed.
> Marking task failed doesn't kill the task when it is run through impersonation(run_as_user)
> -------------------------------------------------------------------------------------------
>
> Key: AIRFLOW-5419
> URL: https://issues.apache.org/jira/browse/AIRFLOW-5419
> Project: Apache Airflow
> Issue Type: Bug
> Components: core
> Affects Versions: 1.10.2
> Reporter: Bharath Palaksha
> Assignee: Bharath Palaksha
> Priority: Major
>
> Airflow dag which is run using "run_as_user" doesn't get killed when SIGTERM signal is sent to the process.
> When task is marked for failure by user or by scheduler - SIGTERM signal is sent to kill the process, but task has a different user id and it requires sudo kill to be killed.
>
--
This message was sent by Atlassian Jira
(v8.3.2#803003)