Elena Ezhova f9b2791735 Prevent calling waitall() inside a GreenPool's greenthread ... When neutron-server is running with several api workers sending it a termination signal (SIGTERM, SIGHUP or SIGINT) leads to waitall() being called inside a GreenPool's greenthread. The reason is that a wsgi server is started in a green thread from the same green pool that is passed to the server itself to be used for spawning client green threads. To avoid it, it is reasonable to use different pools for spawning a wsgi server and for its internal usage. This is also the case for metadata agent running with several metadata workers. Change-Id: I38174396f06fcb29ac0776534ac6494dabb00df6 Closes-Bug: #1423250		2015-03-10 13:43:24 +03:00
..
api	Fix the api job	2015-02-16 20:34:29 -05:00
common	Change L3 agent AdvancedService class to be non-singleton	2015-02-25 19:09:27 -05:00
contrib	Automate host configuration for functional testing	2015-02-14 05:13:03 +00:00
etc	drop unused test rootwrap filter file	2015-01-20 18:09:39 +01:00
functional	Merge "Introduce ip address monitor"	2015-03-05 01:14:11 +00:00
unit	Prevent calling waitall() inside a GreenPool's greenthread	2015-03-10 13:43:24 +03:00
var	Allow combined certificate/key files for SSL	2014-04-13 09:22:23 +00:00
__init__.py	tests: monkey patch stdlib before importing other modules	2015-02-18 13:33:57 +01:00
base.py	oslo: migrate to namespace-less import paths	2015-02-05 15:09:32 +01:00
fake_notifier.py	Pass serializer to oslo.messaging Notifier	2014-06-20 14:58:28 +02:00
post_mortem_debug.py	Cleanup recent generalization in post mortem debugger	2014-12-04 15:28:11 +01:00
sub_base.py	oslo: migrate to namespace-less import paths	2015-02-05 15:09:32 +01:00
tools.py	Refactor Pinger class	2015-02-25 09:38:41 +00:00