airflow-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alessio Palma (JIRA)" <j...@apache.org>
Subject [jira] [Created] (AIRFLOW-1778) Task_instance and Dag_run recycle
Date Thu, 02 Nov 2017 14:30:00 GMT
Alessio Palma created AIRFLOW-1778:
--------------------------------------

             Summary: 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


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
(v6.4.14#64029)

Mime
View raw message