Note:
We have determind that the nova api issue is realted to use both eventlets + wsgi configured to use more then one thread per interpreter instanced.
will allow the nova-api to work correctly with eventlet monkey patching enabled.
when running the nova-api under mod_wsgi or uwsgi
parrallisium shold be managed at teh process level with 1 thread per porcess to avoid this issue
not that the wsgi server will still suspend the python interperter stopping the heartbeat in this
confuration when there are not active api requestion but it will allow concurent cell requests and the heatbeat/amqp connection will automaticaly be resotred when a new request is recived.
Note:
We have determind that the nova api issue is realted to use both eventlets + wsgi configured to use more then one thread per interpreter instanced.
if you are using uswgi setting threads=1
https:/ /uwsgi- docs.readthedoc s.io/en/ latest/ Options. html#threads
or for mod_wsgi
WSGIDaemonProcess ... processes=<api workers> threads=1
https:/ /modwsgi. readthedocs. io/en/develop/ configuration- directives/ WSGIDaemonProce ss.html
will allow the nova-api to work correctly with eventlet monkey patching enabled.
when running the nova-api under mod_wsgi or uwsgi
parrallisium shold be managed at teh process level with 1 thread per porcess to avoid this issue
not that the wsgi server will still suspend the python interperter stopping the heartbeat in this
confuration when there are not active api requestion but it will allow concurent cell requests and the heatbeat/amqp connection will automaticaly be resotred when a new request is recived.