-
Notifications
You must be signed in to change notification settings - Fork 16.6k
Closed
Description
Dear Airflow Maintainers,
Before I tell you about my issue, let me describe my environment:
Environment
- Version of Airflow (e.g. a release version, running your own fork, running off master -- provide a git log snippet):
Airflow 1.7
- Airflow components and configuration, if applicable (e.g. "Running a Scheduler with CeleryExecutor")
running with scheduler & sequential executor
- Example code to reproduce the bug (as a code snippet in markdown)
- Screen shots of your DAG's graph and tree views:
- Stack trace if applicable:
- Operating System: (Windows Version or
$ uname -a)
Red Hat Enterprise Linux Server release 6.6 (Santiago)
- Python Version:
$ python --version
Python 2.7.6
- (Optional) Python packages:
$ pip freezeor$ conda list
Now that you know a little about me, let me tell you about the issue I am having:
Description of Issue
trying to schedule a dag to run at 9 minutes past the hour
- What did you expect to happen?
for airflow to kick off the dag - What happened instead?
nothing - Here is how you can reproduce this issue on your machine:
put this python code in the dag folder
from airflow import DAG
from airflow.operators import BashOperator
from datetime import datetime, timedelta
default_args = {
'owner': 'airflow',
'depends_on_past': False,
'start_date': datetime(2016, 4, 06),
'email_on_failure': True,
'email_on_retry': False,
'retries': 1,
'retry_interval': timedelta(minutes=2),
# 'queue': 'bash_queue',
# 'pool': 'backfill',
# 'priority_weight': 10,
# 'schedule_interval': '50 * * * *',
# 'end_date': datetime(2016, 1, 1),
}
dag = DAG('test_billings2', default_args=default_args,schedule_interval='9 * * * *')
# t1, t2 and t3 are examples of tasks created by instatiating operators
t1 = BashOperator(
task_id='print_date',
bash_command='date',
dag=dag)
t3 = BashOperator(
task_id='test_b',
bash_command='python /home/ec2-user/PyETL/etl_billings_daily.py',
dag=dag)
t3.set_upstream(t1)
Reproduction Steps
- put the python script in the dag folder
- start scheduler
- wait til 9 past the hour and wait for it to run
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels