fzhan commented on issue #41685:
URL: https://github.com/apache/airflow/issues/41685#issuecomment-2342537714
@jscheffl thanks for the update and sorry for late reply, just being
experimenting with different settings.
So after a fresh deployment, with no restriction to the resources, s
fzhan closed issue #41685: worker: Warm shutdown (MainProcess)
URL: https://github.com/apache/airflow/issues/41685
--
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 unsubscrib
jscheffl commented on issue #41685:
URL: https://github.com/apache/airflow/issues/41685#issuecomment-2321101951
Also it would be good - not written in text - was this happening once? After
how many tasks/time? Continously? On how many nodes? Any side effects of failed
tasks?
--
This is a
jscheffl commented on issue #41685:
URL: https://github.com/apache/airflow/issues/41685#issuecomment-2321098170
Warm shutdown is triggered if a SIGINT is raised to the celery process. Can
you please check your K8s events is a liveness probe kicked-in or some
re-balancing in your Kubernetes
boring-cyborg[bot] commented on issue #41685:
URL: https://github.com/apache/airflow/issues/41685#issuecomment-2306090373
Thanks for opening your first issue here! Be sure to follow the issue
template! If you are willing to raise PR to address this issue please do so, no
need to wait for ap
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
