openstack/oslo.log
Code Issues Proposed changes

add a missing link to the release note

Browse Source 
Change-Id: Ia397644458a919045e8c179ae7e974e64073590c
This commit is contained in:
Hervé Beraud 2024-05-16 13:50:54 +02:00 committed by Hervé Beraud
parent 8705f67bfb
commit 9c717f15b3
1 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
releasenotes/notes/remove-eventlet-hub_prevent_multiple_readers-usage-b23cea69a05cd6d4.yaml
View File

@ -4,11 +4,11 @@ fixes:
Remove the usage of the Eventlet debug feature from oslo.log
Then hub_prevent_multiple_readers is a debug convenience. This
feature is a debug convenience. The problem with disabling this
procedure is that it exposes you to risk. Deactivation applies
to the entire stack. If a project uses oslo.log, for example nova,
then it exposes all threads to concurrent access on the process file
descriptors. When several greenlets are reading from the same socket,
it's difficult to predict which greenlet will receive which data. That
services using oslo.log should prefer using tpool rather than un-monkey
patched version of stdlib threading module which is not compatible with
eventlet.
procedure is that `it exposes you to risks <https://eventlet.readthedocs.io/en/latest/reference/api/eventlet.html#eventlet.debug.hub_prevent_multiple_readers>`_.
Deactivation applies to the entire stack. If a project uses oslo.log,
for example nova, then it exposes all threads to concurrent access on
the process file descriptors. When several greenlets are reading from
the same socket, it's difficult to predict which greenlet will receive
which data. That services using oslo.log should prefer using tpool
rather than un-monkey patched version of stdlib threading module which
is not compatible with eventlet.