Closed Bug 1175478 Opened 9 years ago Closed 9 years ago

Update gunicorn from v17.5 to v19.3.0

Categories

(Tree Management :: Treeherder, defect, P2)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: emorley, Assigned: emorley)

References

Details

Attachments

(1 file)

v17.5 was released in 2013.
Given that with bug 1151803 we'll we switching to using gunicorn to serve the static assets too, I think we should update.

http://docs.gunicorn.org/en/latest/2013-news.html
http://docs.gunicorn.org/en/latest/2014-news.html
http://docs.gunicorn.org/en/latest/news.html

https://github.com/benoitc/gunicorn/compare/17.5...19.3
Notable changes:

* switch QUIT and TERM signal
"With this change, when gunicorn receives a QUIT all the workers are killed immediately and exit and TERM is used for the graceful shutdown. Note: the old behaviour was based on the NGINX but the new one is more correct according the following doc:
https://www.gnu.org/software/libc/manual/html_node/Termination-Signals.html
also it is complying with the way the signals are sent by heroku:
https://devcenter.heroku.com/articles/python-faq#what-constraints-exist-when-developing-applications-on-heroku

* honor $WEB_CONCURRENCY environment variable. (Used on heroku)

* log to console by default
Blocks: 1175472
Attachment #8623984 - Flags: review?(mdoglio)
Status: NEW → ASSIGNED
Attachment #8623984 - Flags: review?(mdoglio) → review+
Blocks: 1151803
Looks fine on stage so far :-)
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: