[jira] [Commented] (AIRFLOW-5419) Marking task failed doesn't kill the task when it is run through impersonation(run_as_user)

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AIRFLOW-5419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16923937#comment-16923937 ] 

ASF GitHub Bot commented on AIRFLOW-5419:
-----------------------------------------

bharathpalaksha commented on pull request #6024: AIRFLOW-5419 - Marking task failed doesn't kill the task - https://issues.apache.org/jira/browse/AIRFLOW-5419
URL: https://github.com/apache/airflow/pull/6024
 
 
   Marking task failed doesn't kill the task, when task is run through impersonation(run_as_user)
   
   Make sure you have checked _all_ steps below.
   
   ### Jira
   
   - [ ] My PR addresses the following [Airflow Jira](https://issues.apache.org/jira/browse/AIRFLOW-5419) issues and references them in the PR title.
   
   ### Description
   
   - [ ] When a dag is run through impersonation using 'run_as_user' config. It requires sudo access to be killed when it is marked as 'Failed'
   
   ### Tests
   
   - [ ] Existing test cases should suffice this
   
   ### Commits
   
   - [ ] My commits all reference Jira issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "[How to write a good git commit message](http://chris.beams.io/posts/git-commit/)":
     1. Subject is separated from body by a blank line
     1. Subject is limited to 50 characters (not including Jira issue reference)
     1. Subject does not end with a period
     1. Subject uses the imperative mood ("add", not "adding")
     1. Body wraps at 72 characters
     1. Body explains "what" and "why", not "how"
   
   ### Documentation
   
   - [ ] In case of new functionality, my PR adds documentation that describes how to use it.
     - All the public functions and the classes in the PR contain docstrings that explain what it does
     - If you implement backwards incompatible changes, please leave a note in the [Updating.md](https://github.com/apache/airflow/blob/master/UPDATING.md) so we can assign it to a appropriate release
   
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> 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)