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

   ### Apache Airflow version
   
   2.10.0
   
   ### If "Other Airflow 2 version" selected, which one?
   
   _No response_
   
   ### What happened?
   
   Workers kept going to warm shutdown
   
   Liveness probe failed: Error: No nodes replied within time constraint
   
   worker: Warm shutdown (MainProcess)
   [2024-08-23 02:46:40 +0000] [95] [INFO] Handling signal: term
   [2024-08-23 02:46:40 +0000] [97] [INFO] Worker exiting (pid: 97)
   [2024-08-23 02:46:40 +0000] [96] [INFO] Worker exiting (pid: 96)
   [2024-08-23 02:46:40 +0000] [95] [INFO] Shutting down: Master
   
   ### What you think should happen instead?
   
   The workers use to be alive.
   
   ### How to reproduce
   
   helm repo add apache-airflow https://airflow.apache.org
   helm upgrade --install airflow apache-airflow/airflow --namespace airflow 
--create-namespace
   
   ### Operating System
   
   kubernetes 1.29
   
   ### Versions of Apache Airflow Providers
   
   _No response_
   
   ### Deployment
   
   Official Apache Airflow Helm Chart
   
   ### Deployment details
   
   helm repo add apache-airflow https://airflow.apache.org
   helm upgrade --install airflow apache-airflow/airflow --namespace airflow 
--create-namespace
   
   ### Anything else?
   
   CONNECTION_CHECK_MAX_COUNT=0 exec /entrypoint python -m celery --app 
airflow.providers.celery.executors.celery_executor.app inspect ping -d 
celery@$(hostname)
   Error: No nodes replied within time constraint
   
   ### Are you willing to submit PR?
   
   - [ ] 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