lucidumio commented on issue #55768:
URL: https://github.com/apache/airflow/issues/55768#issuecomment-3361470737
@alkismavridis Thanks for the suggestion!
This is our scheduler section:
` airflow-scheduler:
labels:
com.datadoghq.ad.logs: '[{"source": "airflow", "service":
"airflow-scheduler"}]'
<<: *airflow-common
command: scheduler
healthcheck:
test: ["CMD", "curl", "--fail", "http://localhost:8974/health";]
interval: 30s
timeout: 10s
retries: 5
restart: always
depends_on:
<<: *airflow-common-depends-on
airflow-init:
condition: service_completed_successfully`
The docker-compose did restart the container after the scheduler exited, but
the healthcheck failed soon.
But if we manually run the native docker-compose restart command to bounce
the container, the healthcheck is always good:
`/usr/local/bin/docker-compose restart airflow-scheduler`
--
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]
