You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2021/01/19 10:57:46 UTC

[GitHub] [airflow] raj-manvar commented on issue #10964: No response from gunicorn master within 120 seconds After Changing Worker Class

raj-manvar commented on issue #10964:
URL: https://github.com/apache/airflow/issues/10964#issuecomment-762766717


   We are also facing similar issue and seeing that soon after all workers start, it goes into refresh state.
   ```
   [2021-01-19 09:52:31,771] {cli.py:979} DEBUG - [5 / 5] Killing 1 workers
   [2021-01-19 09:52:31 +0000] [66] [INFO] Handling signal: ttou
   [2021-01-19 09:52:31 +0000] [124] [INFO] Worker exiting (pid: 124)
   ```
   Though in out case we see the gunicorn master not responding error and consequently restart of webserver much later ( after an hour or so, also one hour duration isn't fixed ) 


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org