airflow-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Moritz (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AIRFLOW-669) JobScheduler skips the first dag run
Date Fri, 02 Dec 2016 20:31:59 GMT

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

Eric Moritz updated AIRFLOW-669:
--------------------------------
    Description: 
There appears to be a bug in Airflow's JobScheduler where it does not create the first scheduled
dag run until the second scheduled dag run.

For instance for a DAG with the following properties:

{code:py}
dag = DAG(
            'test_scheduler_dagrun_skips_first',
            start_date=datetime.datetime(2016, 11, 1, 12),
            schedule_interval="00 * * * *"
)
{code}

When the current time is {{2016-11-01T12:01}} the expected behavior is that a dag run will
be scheduled for {{2016-11-01T12:00}} however the {{JobSchedule.create_dag_run()}} method
returns {{None}}

When the current time is {{2016-11-01T12:01}} the expected behavior is that a dag run will
be scheduled for {{2016-11-01T13:00}} however the {{JobSchedule.create_dag_run()}} creates
a DagRun model with the {{execution_date}} of {{2016-11-01T12:00}}.



  was:
There appears to be a bug in Airflow's JobScheduler where it does not create the first scheduled
dag run until the second scheduled dag run.

For instance for a DAG with the following properties:

{code:python}
dag = DAG(
            'test_scheduler_dagrun_skips_first',
            start_date=datetime.datetime(2016, 11, 1, 12),
            schedule_interval="00 * * * *"
)
{code}

When the current time is {{2016-11-01T12:01}} the expected behavior is that a dag run will
be scheduled for {{2016-11-01T12:00}} however the {{JobSchedule.create_dag_run()}} method
returns {{None}}

When the current time is {{2016-11-01T12:01}} the expected behavior is that a dag run will
be scheduled for {{2016-11-01T13:00}} however the {{JobSchedule.create_dag_run()}} creates
a DagRun model with the {{execution_date}} of {{2016-11-01T12:00}}.




> JobScheduler skips the first dag run
> ------------------------------------
>
>                 Key: AIRFLOW-669
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-669
>             Project: Apache Airflow
>          Issue Type: Bug
>    Affects Versions: Airflow 1.8, Airflow 1.7.1.3
>            Reporter: Eric Moritz
>
> There appears to be a bug in Airflow's JobScheduler where it does not create the first
scheduled dag run until the second scheduled dag run.
> For instance for a DAG with the following properties:
> {code:py}
> dag = DAG(
>             'test_scheduler_dagrun_skips_first',
>             start_date=datetime.datetime(2016, 11, 1, 12),
>             schedule_interval="00 * * * *"
> )
> {code}
> When the current time is {{2016-11-01T12:01}} the expected behavior is that a dag run
will be scheduled for {{2016-11-01T12:00}} however the {{JobSchedule.create_dag_run()}} method
returns {{None}}
> When the current time is {{2016-11-01T12:01}} the expected behavior is that a dag run
will be scheduled for {{2016-11-01T13:00}} however the {{JobSchedule.create_dag_run()}} creates
a DagRun model with the {{execution_date}} of {{2016-11-01T12:00}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message