You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@airflow.apache.org by "jack (Jira)" <ji...@apache.org> on 2019/09/25 10:00:16 UTC

[jira] [Commented] (AIRFLOW-1778) Task_instance and Dag_run recycle

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

jack commented on AIRFLOW-1778:
-------------------------------

Deleting a dag run also delete the tasks

> Task_instance and Dag_run recycle
> ---------------------------------
>
>                 Key: AIRFLOW-1778
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-1778
>             Project: Apache Airflow
>          Issue Type: Wish
>          Components: DagRun
>    Affects Versions: 1.8.1
>            Reporter: Alessio Palma
>            Priority: Trivial
>
> Hello, I'm not sure this is a real issue but something strange happened on our airflow installation.
> We started a dag which did not complete due to some issues on Hadoop, so we delete all the dag_run affected and left untouched the task_instances  waited for it to complete but... 
> 1. Every dag restarted with the correct execution date
> 2. No processor executed for real
> 3. airflow used the old task_instance record.
> So the question is... it was so bad just to delete the dag_run without deleting the task_instances?  Also... If it is bad to delete the dag_run, why it is possible to execute this action from the admin menu? 
> Should the delete dag_run option to be removed? 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)