You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Peter Erben (JIRA)" <ji...@apache.org> on 2019/01/09 15:15:00 UTC
[jira] [Created] (AIRFLOW-3658) dag.get_run_dates() goes into
infinite loop in case of missing date, cause by DST switch
Peter Erben created AIRFLOW-3658:
------------------------------------
Summary: dag.get_run_dates() goes into infinite loop in case of missing date, cause by DST switch
Key: AIRFLOW-3658
URL: https://issues.apache.org/jira/browse/AIRFLOW-3658
Project: Apache Airflow
Issue Type: Bug
Components: DAG
Affects Versions: 1.10.1
Environment: ubuntu 16.04
python 3.6
airflow 1.10.1
Reporter: Peter Erben
In airflow.cfg the default_timezone is Europe/Budapest. In this timezone the winter to summer DST switch happened on 2018-03-25 at 2am, when the the the hour skipped to 3am. This means that 2018-03-24T02:00:00 is not a valid datetime in that timezone.
I created a dag with these parameters:
{{start_date = datetime(2018,3,25,0,0) - timedelta(days=2)}}
{{end_date = datetime(2018,3,25,0,0) + timedelta(days=2)}}
{{schedule_interval = '0 2 * * *'}}
When I call dag.get_run_dates(), it never returns.
Does this means, that Airflow fails to schedule any tasks if I try to set the Europe/Budapest timezone, and the daily time defined by the cronstring is non-existent on the day of the DST switch?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)