]> review.fuel-infra Code Review - openstack-build/cinder-build.git/commit
Eventlet green threads not released back to pool
authorabhishekkekane <abhishek.kekane@nttdata.com>
Tue, 21 Oct 2014 09:31:15 +0000 (02:31 -0700)
committerabhishekkekane <abhishek.kekane@nttdata.com>
Fri, 24 Oct 2014 21:35:46 +0000 (14:35 -0700)
commitfc87da7eeb3451e139ee71b31095d0b9093332ce
treec6fc11eab57e38f6c284d8e6153e07cd3e0218fb
parent2cb1aaf69d17963cc7205002fa194b3b41b51d5f
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 wsgi_keep_alive option (default=True).
In order to maintain the backward compatibility, setting wsgi_keep_alive
as True by default. Recommended is set it to False.

SecurityImpact

Closes-Bug: #1361360
Change-Id: Ic57b2aceb136e8626388cfe4df72b2f47cb0661c
cinder/wsgi.py
etc/cinder/cinder.conf.sample