Eventlet green threads not released back to pool
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
openstack-manuals |
Fix Released
|
Medium
|
Unassigned |
Bug Description
https:/
Dear documentation bug triager. This bug was created here because we did not know how to map the project name "openstack/heat" to a launchpad project name. This indicates that the notify_impact config needs tweaks. You can ask the OpenStack infra team (#openstack-infra on freenode) for help if you need to.
commit 2be72f42f9debf9
Author: yangxurong <email address hidden>
Date: Mon Mar 30 14:39:17 2015 +1000
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.
Add 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
Change-Id: I303d87addeed8b
Closes-Bug: #1361360
Changed in openstack-manuals: | |
milestone: | none → liberty |
status: | New → Confirmed |
importance: | Undecided → Medium |
tags: | added: autogenerate-config-docs |
Changed in openstack-manuals: | |
milestone: | liberty → mitaka |
Changed in openstack-manuals: | |
status: | Fix Committed → Triaged |
milestone: | mitaka → newton |
Changed in openstack-manuals: | |
status: | Triaged → Fix Released |
This affects the table and is updated in rst version config-reference : /github. com/openstack/ openstack- manuals/ blob/master/ doc/config- reference/ source/ tables/ heat-api. rst
https:/