[
https://issues.apache.org/jira/browse/AIRFLOW-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17009187#comment-17009187
]
ASF GitHub Bot commented on AIRFLOW-4428:
-----------------------------------------
potiuk commented on pull request #6948: [AIRFLOW-4428] error if exec_date
before default_args.start_date in t…
URL: https://github.com/apache/airflow/pull/6948
----------------------------------------------------------------
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:
[email protected]
> 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: Improvement
> Components: DAG, DagRun, scheduler
> Affects Versions: 1.10.3
> Environment: LocalExecutor, 16cpu amazon linux, airflow 1.10.3, mysql
> RDS meta
> Reporter: t oo
> Assignee: 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
> the below jira caused it:
> * https://github.com/apache/airflow/pull/4808/files
> (https://issues.apache.org/jira/browse/AIRFLOW-3982)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
