[ 
https://issues.apache.org/jira/browse/AIRFLOW-1328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16057198#comment-16057198
 ] 

Pierre-Antoine Tible edited comment on AIRFLOW-1328 at 6/21/17 8:52 AM:
------------------------------------------------------------------------

Okay, it's quite strange, because i know it bas been executed just now, but the 
execution date is yesterday. I don't understand why it was make like this. I 
understand how the next scheduled interval works but there it was the first 
launch.
The start_date is set to now() - 1 day but as he does a start_date + 
schedule_interval, so I though it will execute it the current day.

I have one other question, last night I scheduled two tasks for the first time, 
at 3 am, the python script is almost the same but one was executed, not the 
other. My 6am task was not executed either. Any idea ? The start_date is now() 
- (1 day + 6 seconds) and the schedule_interval 
[http://imgur.com/a/4y6HN]



was (Author: zhajor):
Okay, it's quite strange, because i know it bas been executed just now, but the 
execution date is yesterday. I don't understand why it was make like this. I 
understand how the next scheduled interval works but there it was the first 
launch.
The start_date is set to now() - 1 day but as he does a start_date + 
schedule_interval, so I though it will execute it the current day.

I have one other question, last night I scheduled two tasks for the first time, 
at 3 am, the python script is almost the same but one was executed, not the 
other. My 6am task was not executed either. Any idea ? The start_date is now() 
- (1 day + 6 seconds) and the schedule_interval 
!http://imgur.com/a/4y6HN!


> Daily DAG execute the past day
> ------------------------------
>
>                 Key: AIRFLOW-1328
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-1328
>             Project: Apache Airflow
>          Issue Type: Bug
>          Components: DagRun
>    Affects Versions: Airflow 1.8
>         Environment: debian jessie
>            Reporter: Pierre-Antoine Tible
>
> Hello,
> I'm running Airflow 1.8 under debian jessie. I installed it via pip.
> I am using the LocalScheduler with a Mysql.
> I made a simple DAG with a BashOperator for a daily task (two times) : 
> +_default_args = {
>     'owner': 'airflow',
>     'depends_on_past': False,
>     'start_date': datetime.now() - timedelta(days=1, seconds=6),
>     'email': ['XXX'],
>     'email_on_failure': True,
>     'email_on_retry': False,
>     'retries': 1,
>     'retry_delay': timedelta(minutes=5),
>     'execution_timeout': None,
>     #'catchup': False,
>     #'backfill': False,
>     # 'queue': 'bash_queue',
>     # 'pool': 'backfill',
>     # 'priority_weight': 10,
>     # 'end_date': datetime(2016, 1, 1),
> }
> dag = DAG('campaign-reminder', default_args=default_args, 
> schedule_interval="0,0 7,15 * * *", concurrency=1, max_active_runs=1)
> dag.catchup = False
> t1 = BashOperator(
>     task_id='campaign-reminder',
>     bash_command='XXXX ',
>     dag=dag)_+
> I did it today, it works, but the execution date was "06-19T15:00:00", we are 
> the 20th, so it's one day behind the schedule.
> My first though was a mistake with the start_date, so I put a datetime() and 
> it did the same ...
> I don't understand why.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to