yeachan153 opened a new issue, #24332:
URL: https://github.com/apache/airflow/issues/24332
### Apache Airflow version
2.1.4
### What happened
Workers are not finishing their graceful shutdown, seems to be getting stuck
at `[2022-06-08 15:42:28,225: DEBUG/MainProcess] | Worker: Stopping Pool...`
```md
worker: Warm shutdown (MainProcess)
[2022-06-08 15:42:28,211: DEBUG/MainProcess] | Worker: Closing Hub...
[2022-06-08 15:42:28,211: DEBUG/MainProcess] | Worker: Closing Pool...
[2022-06-08 15:42:28,211: DEBUG/MainProcess] | Worker: Closing Consumer...
[2022-06-08 15:42:28,211: DEBUG/MainProcess] | Worker: Stopping Consumer...
[2022-06-08 15:42:28,211: DEBUG/MainProcess] | Consumer: Closing
Connection...
[2022-06-08 15:42:28,211: DEBUG/MainProcess] | Consumer: Closing Events...
[2022-06-08 15:42:28,211: DEBUG/MainProcess] | Consumer: Closing Mingle...
[2022-06-08 15:42:28,211: DEBUG/MainProcess] | Consumer: Closing Tasks...
[2022-06-08 15:42:28,211: DEBUG/MainProcess] | Consumer: Closing Control...
[2022-06-08 15:42:28,211: DEBUG/MainProcess] | Consumer: Closing Gossip...
[2022-06-08 15:42:28,211: DEBUG/MainProcess] | Consumer: Closing Heart...
[2022-06-08 15:42:28,212: DEBUG/MainProcess] | Consumer: Closing event
loop...
[2022-06-08 15:42:28,212: DEBUG/MainProcess] | Consumer: Stopping event
loop...
[2022-06-08 15:42:28,212: DEBUG/MainProcess] | Consumer: Stopping Heart...
[2022-06-08 15:42:28,213: DEBUG/MainProcess] | Consumer: Stopping Gossip...
[2022-06-08 15:42:28,223: DEBUG/MainProcess] | Consumer: Stopping Control...
[2022-06-08 15:42:28,225: DEBUG/MainProcess] | Consumer: Stopping Tasks...
[2022-06-08 15:42:28,225: DEBUG/MainProcess] Canceling task consumer...
[2022-06-08 15:42:28,225: DEBUG/MainProcess] | Consumer: Stopping Mingle...
[2022-06-08 15:42:28,225: DEBUG/MainProcess] | Consumer: Stopping Events...
[2022-06-08 15:42:28,225: DEBUG/MainProcess] | Consumer: Stopping
Connection...
[2022-06-08 15:42:28,225: DEBUG/MainProcess] | Worker: Stopping Pool...
[2022-06-08 15:42:53,351] {_internal.py:113} INFO - 10.35.33.144 - -
[08/Jun/2022 15:42:53] "GET /log/health HTTP/1.1" 200 -
[2022-06-08 15:43:23,351] {_internal.py:113} INFO - 10.35.33.144 - -
[08/Jun/2022 15:43:23] "GET /log/health HTTP/1.1" 200 -
```
10 minutes later this was still the same state.
### What you think should happen instead
The worker should finish it's shutdown process and exit.
### How to reproduce
1. Select celery executor
2. Set DUMB_INIT_SETSID=0 as part of the env var of the worker
3. Trigger worker termination
### Operating System
Debian GNU/Linux 10 (buster)
### Versions of Apache Airflow Providers
apache-airflow-providers-amazon==2.2.0
apache-airflow-providers-celery==2.0.0
apache-airflow-providers-cncf-kubernetes==2.0.2
apache-airflow-providers-docker==2.1.1
apache-airflow-providers-elasticsearch==2.0.3
apache-airflow-providers-ftp==2.0.1
apache-airflow-providers-google==5.1.0
apache-airflow-providers-grpc==2.0.1
apache-airflow-providers-hashicorp==2.1.0
apache-airflow-providers-http==2.0.1
apache-airflow-providers-imap==2.0.1
apache-airflow-providers-microsoft-azure==3.1.1
apache-airflow-providers-mysql==2.1.1
apache-airflow-providers-odbc==2.0.1
apache-airflow-providers-postgres==2.2.0
apache-airflow-providers-redis==2.0.1
apache-airflow-providers-sendgrid==2.0.1
apache-airflow-providers-sftp==2.1.1
apache-airflow-providers-slack==4.0.1
apache-airflow-providers-sqlite==2.0.1
apache-airflow-providers-ssh==2.1.1
### Deployment
Other Docker-based deployment
### Deployment details
We are using apache/airflow:2.1.4-python3.7 as the base image, and deploying
the components in Kubernetes (GKE):
Airflow Webserver (x2)
Airflow Scheduler (x2)
Airflow Worker (x6)
Redis broker
### Anything else
Using celery executor
### 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]
