openstack/mistral
Code Issues Proposed changes

Release note for adding "oslo_rpc_executor" config option

Browse Source 
Change-Id: Iddd02f3f428cc0ab68a7a301cf5f5db19f6a083a
Closes-Bug: #1696469
This commit is contained in:
Renat Akhmerov 2018-07-19 12:08:04 +07:00
parent 0448383d20
commit d3305c709e
1 changed files with 17 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
releasenotes/notes/add_config_option_for_oslo_rpc_executor-44afe1f728afdcb2.yaml Normal file
View File

@ -0,0 +1,17 @@
---
features:
- |
Added the config option "oslo_rpc_executor" sets an executor type used by
Oslo Messaging framework. Defines how Oslo Messaging based RPC subsystem
processes incoming calls. Allowed values: "eventlet", "threading" and
"blocking". However, "blocking" is deprecated by the Oslo Messaging team
and may be removed in the next versions.
The reason of adding this option was in the issues occuring when using
MySQLDb database driver and "eventlet" RPC executor. Once in a while,
the system would hang on a deadlock caused by the fact that the DB
driver wasn't eventlet-friendly and dispatching of green threads didn't
work properly. That's why "blocking" was used. Now it's been proven that
a combination of "eventlet" executor and PyMysql driver works well. The
configuration option for the RPC executor though allows to rollback to
"blocking" in case if regression is found, or also experiment with
"threading".