You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by ka...@apache.org on 2026/10/01 20:52:28 UTC

(airflow) branch main updated: Clarify `max_db_retries` doc wording to avoid off-by-one confusion (#73722)

This is an automated email from the ASF dual-hosted git repository.

kaxil pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/airflow.git


The following commit(s) were added to refs/heads/main by this push:
     new 7d6244bf191 Clarify `max_db_retries` doc wording to avoid off-by-one confusion (#73722)
7d6244bf191 is described below

commit 7d6244bf191e8913c2bc74cd66b6ea0ca6995821
Author: soham waghe <11...@users.noreply.github.com>
AuthorDate: Fri Oct 2 02:22:19 2026 +0530

    Clarify `max_db_retries` doc wording to avoid off-by-one confusion (#73722)
    
    closes: #73715
---
 airflow-core/src/airflow/config_templates/config.yml | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/airflow-core/src/airflow/config_templates/config.yml b/airflow-core/src/airflow/config_templates/config.yml
index cc8f4c54c05..34849d5eb5e 100644
--- a/airflow-core/src/airflow/config_templates/config.yml
+++ b/airflow-core/src/airflow/config_templates/config.yml
@@ -759,9 +759,9 @@ database:
       default: ~
     max_db_retries:
       description: |
-        Number of times the code should be retried in case of DB Operational Errors.
-        Not all transactions will be retried as it can cause undesired state.
-        Currently it is only used in ``DagFileProcessor.process_file`` to retry ``dagbag.sync_to_db``.
+        Maximum number of attempts, including the first one, for operations retried on DB
+        operational errors. The default of 3 means one initial attempt plus up to 2 retries.
+        Not all transactions are retried, since retrying some of them can leave undesired state.
       version_added: 2.3.0
       type: integer
       example: ~