Eventlet green threads not released back to pool
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
openstack-manuals |
Fix Released
|
Medium
|
Gauvain Pocentek |
Bug Description
https:/
commit a657582c5cd8a39
Author: abhishekkekane <email address hidden>
Date: Tue Oct 21 01:37:42 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.
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_
Conflicts:
Note: The required unit-tests are manually added to the below path,
as new path for unit-tests is not present in stable/icehouse release.
nova/
This patch is not 1:1 cherry-pick, I have changed the default value
of client_
stable branches.
(https:/
SecurityImpact
Closes-Bug: #1361360
Change-Id: I399b812f6d4522
(cherry picked from commit 04d7a724fdf80db
Changed in openstack-manuals: | |
status: | New → Triaged |
milestone: | none → kilo |
importance: | Undecided → Medium |
tags: | added: autogenerate-config-docs |
Changed in openstack-manuals: | |
status: | Triaged → Fix Released |
assignee: | nobody → Gauvain Pocentek (gpocentek) |