You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "jack (JIRA)" <ji...@apache.org> on 2019/04/18 12:23:00 UTC
[jira] [Commented] (AIRFLOW-2943) example_trigger_target_dag.py Dag
is stuck in running state
[ https://issues.apache.org/jira/browse/AIRFLOW-2943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16821029#comment-16821029 ]
jack commented on AIRFLOW-2943:
-------------------------------
Can you recheck this with master?
Airflow had extensive upgrade regarding timezones.
> example_trigger_target_dag.py Dag is stuck in running state
> -----------------------------------------------------------
>
> Key: AIRFLOW-2943
> URL: https://issues.apache.org/jira/browse/AIRFLOW-2943
> Project: Apache Airflow
> Issue Type: Bug
> Affects Versions: 1.8.0
> Environment: Python 2.7
> Reporter: Loveleen Kaur
> Priority: Critical
> Attachments: airflow issue.PNG
>
>
> Hi,
> I am trying to implement example_trigger_controller_dag.py and example_trigger_target_dag.py (according to my requirements) but the execution time of target dag is approximately 7 hours more than the triggered time i.e Triggered time is in PDT but the execution time of dag is showing in UTC. These sample examples are giving same issue. Because of this Dag run after 7 hours of the triggered time.
> In Issue - Apache AirflowAIRFLOW-43 , it is mentioned -
> If you see the dag run created, but not being scheduled, it is likely because you are not running in UTC everywhere.
> Airflow dags are running in PDT timezone , so to convert that into UTC, i updated cfg file with default_timezone = utc and restarted airflow but still getting same issue.
> Please help.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)