When encountered with this issue some projects in OpenStack using
oslo.log, eg. Cinder, resolve them by removing any logging withing
native threads.
There is actually a better approach. The Swift team came up with a
solution a long time ago [1], and in this patch that fix is included as
part of the setup method, but will only be run if the eventlet library
has already been loaded.
This patch adds the eventlet library as a testing dependency for the
PipeMutext unit tests.
Reviewed: https:/ /review. opendev. org/c/openstack /oslo.log/ +/852443 /opendev. org/openstack/ oslo.log/ commit/ 94b9dc32ec1f52a 582adbd97fe2847 f7c87d6c17
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit 94b9dc32ec1f52a 582adbd97fe2847 f7c87d6c17
Author: Gorka Eguileor <email address hidden>
Date: Mon Aug 8 16:44:20 2022 +0200
Fix logging in eventlet native threads
There is a bug in eventlet where logging within a native thread can lead /github. com/eventlet/ eventlet/ issues/ 432
to a deadlock situation: https:/
When encountered with this issue some projects in OpenStack using
oslo.log, eg. Cinder, resolve them by removing any logging withing
native threads.
There is actually a better approach. The Swift team came up with a
solution a long time ago [1], and in this patch that fix is included as
part of the setup method, but will only be run if the eventlet library
has already been loaded.
This patch adds the eventlet library as a testing dependency for the
PipeMutext unit tests.
[1]: https:/ /opendev. org/openstack/ swift/commit/ 69c715c505cf9e5 df29dc1dff2fa1a 4847471cb6
Closes-Bug: #1983863 e4b95964e6cdc0f f2483a4e57d
Change-Id: Iac1b0891ae584c