GitHub user jradhima added a comment to the discussion: Need help understanding total number of Dags oscillating on UI
Thanks for the reply. I understand the configuration settings, I just don't understand the design decision taken. The point of the standalone dag processor is that the scheduler only schedules and doesn't need to have access to the dag files. Why is airflow bypassing this by faking access to this information? Shouldn't the dags be a responsibility of the processor and the scheduler just schedules? I think it's more intuitive that when a dag file is removed or the source code of a dag is modified and the dag becomes stale, the dag processor removes it instead of the scheduler. This way, if you have any issues, you only need to check one place in the code/logs/configuration to figure out the behavior. GitHub link: https://github.com/apache/airflow/discussions/44495#discussioncomment-12233227 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
