bluek1te commented on issue #27399:
URL: https://github.com/apache/airflow/issues/27399#issuecomment-1315575328
Steps to reproduce this (with other bug that reloads DAGs in order of
milliseconds):
> Set environment variable TZ to UTC. (Or leave unset if UTC by default)
> Set environment variable AIRFLOW__CORE__DEFAULT_TIMEZONE=America/Chicago
> Create new DAG (this DAG must not currently be in the database) that uses
CronTriggerTimetable, we used this:
```
with DAG(
'cron-trigger-test-repeat-new',
description='cron-trigger-reproduce-bug',
catchup=False,
schedule=CronTriggerTimetable(f'* * * * *',
timezone='America/Chicago'),
default_args = {
'start_date': datetime(2022, 1, 1),
'depends_on_past': False,
'timezone': "America/Chicago"
},
is_paused_upon_creation=False
) as echo:
hello = BashOperator(
task_id="echo",
bash_command="echo Hello World!"
)
echo
```
> Wait for DAG to be picked up by the scheduler
> Observe that the last_parsed_time in the dag table in airflow database (we
use postgres) is updating wayyyy faster than it needs to.
> Observe that the DAG has a lot of missed runs every minute (we get less
than 50% to trigger on schedule when we do this)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
