Andrushika opened a new pull request, #73167: URL: https://github.com/apache/airflow/pull/73167
Stack on #72567; this should be dealt with after that PR is merged. ## Why `breeze start-airflow` starts the postgres or mysql container first and waits until Docker marks it healthy before starting the airflow container. Docker Engine 25 probes the healthcheck every `start_interval` during `start_period`, and the default is 5 seconds. A fresh postgres container is usually ready in 2 to 3 seconds, so the first probe at 5 seconds is the thing everyone waits for. ## What Only two line changes: Add `start_interval: 1s` to the postgres and mysql healthchecks in `scripts/ci/docker-compose/`. Failed probes inside `start_period` do not count toward `retries`, and after `start_period` the normal `interval: 10s` applies as before. Measured on a fresh postgres container, from `compose up` to the airflow container being allowed to start: | | before | after | |---|---|---| | postgres ready | 7.75s | 3.4s | `start_interval` needs Docker Engine 25 and Compose 2.20.2, which are already the minimum versions breeze checks for in `global_constants.py`. related: #72567 --- ##### Was generative AI tooling used to co-author this PR? - [X] Yes — Claude Code (Fable 5.1) Generated-by: Claude Code (Fable 5.1) following [the guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions) -- 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]
