xuganyu96 opened a new issue, #31818:
URL: https://github.com/apache/airflow/issues/31818

   ### Description
   
   In my company usage of Airflow, developmental instances of Airflow run on 
containerized PostgreSQL that are spawned at the same time the Airflow 
container is spawned. Before the Airflow container runs its initialization 
scripts, it needs to make sure that the PostgreSQL instance can be reached, for 
which `airflow db check` is a great option.
   
   However, there is a non-deterministic race condition between the PSQL 
container and Airflow containers (not sure which will each readiness first and 
by how much), calling the `airflow db check` command once is not sufficient, 
and implementing a retry-timeout in shell script is feasible but unpleasant.
   
   It would be great if the `airflow db check` command can take two additional 
optional arguments: `--retry` and `--retry-delay` (just like with `curl`) so 
that the database connection can be checked repeatedly for up to a specified 
number of times. This command should exit with `0` exit code if any of the 
retries succeeds, and `1` if all of the retries failed.
   
   ### Use case/motivation
   
   _No response_
   
   ### Related issues
   
   _No response_
   
   ### Are you willing to submit a PR?
   
   - [X] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


-- 
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]

Reply via email to