[jira] [Updated] (AIRFLOW-4428) Externally triggered DagRun marked as 'success' state but all tasks for it are 'None' state

["t oo (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/AIRFLOW-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

t oo updated AIRFLOW-4428:
--------------------------
    Summary: Externally triggered DagRun marked as 'success' state but all tasks for it are 'None' state  (was: Dag run marked as 'success' state but all tasks for it are 'None' state)

> Externally triggered DagRun marked as 'success' state but all tasks for it are 'None' state
> -------------------------------------------------------------------------------------------
>
>                 Key: AIRFLOW-4428
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-4428
>             Project: Apache Airflow
>          Issue Type: Bug
>          Components: DAG, DagRun, scheduler
>    Affects Versions: 1.10.3
>         Environment: LocalExecutor, 16cpu amazon linux, airflow 1.10.3, mysql RDS meta
>            Reporter: t oo
>            Priority: Critical
>         Attachments: Screenshot from 2019-05-10 10-42-53.png, graph.png
>
>
> Dagrun status showing success for a given execdate but:
> *  all tasks are white in graph/tree view
> *  on cli running airflow task_state for any of the tasks showing in the graph/tree view returns None
> * taskinstance view shows no tasks for the given dagid
> This dag has 800 tasks, non_pooled_task_slot_count is 2000, max_tis_per_query is 2000, no pools created/assigned to the dag
> This is an externally triggered dag, all my dags are purely externally triggered.
> For execdates 20150101, 20160101, 20170101 getting this issue but 20180101 works. Maybe it has something to do with this line in my dag mentioning 2017 ---> default_args = {'owner': 'airflow','start_date': dt.datetime(2017, 6, 1),'retries': 0,'retry_delay': dt.timedelta(minutes=5),}
> As per comments below this issue was introduced in 1.10.3. release, i suspect one of the below jiras caused it:
> * https://github.com/apache/airflow/pull/4781/files  (https://issues.apache.org/jira/browse/AIRFLOW-3962)
> * https://github.com/apache/airflow/pull/4808/files  (https://issues.apache.org/jira/browse/AIRFLOW-3982)
> * https://github.com/apache/airflow/pull/4618/files  (https://issues.apache.org/jira/browse/AIRFLOW-3462)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)