airflow-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Driesprong, Fokko" <fo...@driesprong.frl>
Subject Re: DagRunOperator - target dag tasks are not triggered - possible timezone conflict
Date Fri, 06 Jul 2018 20:39:33 GMT
Hi Niranda,

What version of Airflow are you running? There are a lot of improvements
coming up in Airflow 1.10 regarding timezones.

https://github.com/apache/incubator-airflow/blob/master/airflow/config_templates/default_airflow.cfg#L77-L79

Cheers, Fokko



2018-07-05 14:57 GMT+02:00 Niranda Perera <niranda.17@cse.mrt.ac.lk>:

> Hi,
>
> I am checking the DagRunOperator [1] and I was using the
> example_trigger_controller_dag.py & example_trigger_target_dag.py.
>
> When I triggered the controller dag, the target dag tasks are not
> triggered.
> Check dags.png
>
> while investigating further (check dagruns.png), I believe this due to dag
> run execution date setting. I am in UTC+5.30 and while the controller dag
> execution time was set by UTC+0, the target dag execution was set by my
> local timezone UTC+5.30. So, the target would not get triggered for another
> 5.30 hours.
>
> so, Is there a way to bind the timezones in airflow?
>
> [1] https://airflow.apache.org/_modules/dagrun_operator.html
>
> Best regards
>
> Niranda Perera
> Research Assistant
> Dept of CSE, University of Moratuwa
> niranda.17@cse.mrt.ac.lk
> +94 71 554 8430
> https://lk.linkedin.com/in/niranda
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message