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