You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Jarek Potiuk (Jira)" <ji...@apache.org> on 2020/01/19 23:37:07 UTC

[jira] [Closed] (AIRFLOW-876) Change or document default gunicorn worker class

     [ https://issues.apache.org/jira/browse/AIRFLOW-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jarek Potiuk closed AIRFLOW-876.
--------------------------------
    Resolution: Won't Fix

I am closing some old issues that are not relevant any more. Please let me know if you want to reopen it.

> Change or document default gunicorn worker class
> ------------------------------------------------
>
>                 Key: AIRFLOW-876
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-876
>             Project: Apache Airflow
>          Issue Type: Improvement
>            Reporter: Peter Marton
>            Priority: Minor
>
> The sync gunicorn worker class is not production ready unless behind a proxy like nginx. This is clearly documented in the gunicorn docs, but never mentioned anywhere in the Airflow docs. I feel that either the default should be changed to one of the asynchronous models or users should be adequately warned.
> What makes this even more painful is that AWS ELB tries to keep open the connections for health checks, essentially DOSing the Airflow webserver if used with the default config. But it happens with Chrome's URL preloading as well as mentioned in the link below.
> More info:
> https://www.mail-archive.com/dev@airflow.incubator.apache.org/msg00746.html
> http://stackoverflow.com/questions/21634680/running-unicorn-behind-amazon-elb



--
This message was sent by Atlassian Jira
(v8.3.4#803005)