Eventlet green threads not released back to pool
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| openstack-manuals |
Fix Released
|
Undecided
|
Gauvain Pocentek | ||
Bug Description
https:/
commit d569ed9db9dc194
Author: abhishekkekane <email address hidden>
Date: Tue Oct 21 04:39:59 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.
DocImpact:
Added http_keepalive option (default=True).
Conflicts:
SecurityImpact
Closes-Bug: #1361360
Change-Id: I93aaca24935a4f
(cherry picked from commit 16a821e00d15520
| Lana (loquacity) wrote | #1 |
| Changed in openstack-manuals: | |
| status: | New → Confirmed |
| OpenStack Infra (hudson-openstack) wrote Fix proposed to openstack-manuals (master) | #2 |
| Changed in openstack-manuals: | |
| assignee: | nobody → Gauvain Pocentek (gpocentek) |
| status: | Confirmed → In Progress |
| OpenStack Infra (hudson-openstack) wrote Fix merged to openstack-manuals (master) | #3 |
| Changed in openstack-manuals: | |
| status: | In Progress → Fix Released |
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/openstack-manuals 15.0.0 | #4 |
This needs to be updated in the Config Ref.