This is an automated email from the ASF dual-hosted git repository. ephraimanierobi pushed a commit to branch v2-8-test in repository https://gitbox.apache.org/repos/asf/airflow.git
commit c3ebe74a0dfbdc9ea37c0a9a6c493eae1f57c614 Author: Elad Kalif <[email protected]> AuthorDate: Wed Mar 6 00:29:01 2024 +0200 Clarify lack of sync between workers and scheduler (#37913) * Clarify lack of sync between workers and scheduler * Update docs/apache-airflow/core-concepts/overview.rst --------- Co-authored-by: Jarek Potiuk <[email protected]> (cherry picked from commit 2867951ce0483d99c4c3025a8c64e6076d492d46) --- docs/apache-airflow/core-concepts/overview.rst | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/apache-airflow/core-concepts/overview.rst b/docs/apache-airflow/core-concepts/overview.rst index 9ee9ea8b0b..c49de8d17c 100644 --- a/docs/apache-airflow/core-concepts/overview.rst +++ b/docs/apache-airflow/core-concepts/overview.rst @@ -181,6 +181,14 @@ executed in the context of the scheduler. .. image:: ../img/diagram_dag_processor_airflow_architecture.png +.. note:: + + When DAG file is changed there can be cases where the scheduler and the worker will see different + versions of the DAG until both components catch up. You can avoid the issue by making sure dag is + deactivated during deployment and reactivate once finished. If needed, the cadence of sync and scan + of DAG folder can be configured. Please make sure you really know what you are doing if you change + the configurations. + .. _overview:workloads: Workloads
