potiuk commented on issue #17191: URL: https://github.com/apache/airflow/issues/17191#issuecomment-918968871
Agree - http would make more sense and one healthcheck will be more than enough. I generally prefer `http` kind of healthchecks over exec, as they are more "versatile". Http healthcheck can be used in basically any execution environment and they are generally much safer. You do not need any special permissions to execute the health-check. In many enterprise environments you might simply not get permissions to execute an arbitrary command inside a running container from the monitoring services. If we already have an `http` server there, it's not even a question of adding new dependencies/opening ports etc, because it is already there, so there are no drawbacks of this solution IMHO. Squential is lilkely not a problem, but yeah with Local we have ``--skip-serve-logs`` command - I think it would have to similar ``--skip-healthcheck` and the standalone gunicorn should be started when either logs or health-checks are enabled. -- 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]
