GitHub user jhulme closed a discussion: Pod startupProbe failing because airflow version command slow to execute
I'm having problems with a GKE Cloud Composer installation running Airflow 2.9.1. where the airflow-scheduler pod fails to become ready. After digging in, I've isolated the issue to the `airflow-scheduler` container failing to pass the `startupProbe` check. The check itself simply executes the following command: ``` test -f /etc/airflow/airflow.cfg && airflow version ``` I connected to the pod directly and confirmed that the /etc/airflow/airflow.cfg file is present ruling out that as the cause of the failure. However when executing the `airflow version` command, I found execution time took close to 90secs and at times almost 2 minutes. For now I've adjusted the `periodSeconds` and `timeoutSeconds` values for the `startupProbe` in order to resolve the problem. What I'd like to understand is why the command is taking so long to execute, particularly if this is an issue with our configuration in some manner. As suggested within some of the other issues discussing similar problems I have used `py-spy` to generate a flamegraph and I've attached it for reference. If anyone can help provide some guidance as to where I can start looking in order to speed up execution that would be really appreciated.  GitHub link: https://github.com/apache/airflow/discussions/43447 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
