Eventlet green threads not released back to pool
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
openstack-manuals |
Fix Released
|
Low
|
Tom Fifield |
Bug Description
https:/
commit 8e7a0dbb12082f6
Author: abhishekkekane <email address hidden>
Date: Tue Oct 21 04:15:15 2014 -0700
Eventlet green threads not released back to pool
Presently, the wsgi server allows persist connections. Hence even after
the response is sent to the client, it doesn't close the client socket
connection. Because of this problem, the green thread is not released
back to the pool.
In order to close the client socket connection explicitly after the
response is sent and read successfully by the client, you simply have to
set keepalive to False when you create a wsgi server.
Added a parameter to take advantage of the new(ish) eventlet socket timeout
behaviour. Allows closing idle client connections after a period of time, eg:
$ time nc localhost 8776
real 1m0.063s
Setting 'client_
DocImpact:
Added wsgi_keep_alive option (default=True).
Added client_
SecurityImpact
Closes-Bug: #1361360
Change-Id: I3a361d6590d180
tags: | added: autogenerate-config-docs |
Changed in openstack-manuals: | |
milestone: | none → kilo |
status: | New → Confirmed |
importance: | Undecided → Low |
Changed in openstack-manuals: | |
assignee: | nobody → Tom Fifield (fifieldt) |
status: | Confirmed → In Progress |
https:/ /review. openstack. org/#/c/ 177283/