The debug loggers are pre-created during process startup,
and any that are missing can be created using lazy init.
However the lazy init is not multi process safe and can
lead to a subprocess deadlock during the import phase, which
produces no logs or evidence that the thread is stalled.
The workaround at the moment is to ensure that all the debug
loggers defined at import time are configured to be setup when
the process is created.
There is still another cause of a stall. A separate commit
will address it.
Reviewed: https:/ /review. opendev. org/c/starlingx /nfv/+/ 788759 /opendev. org/starlingx/ nfv/commit/ 1d7e5be68aa1d8a a167244411d1828 bfc3e3d787
Committed: https:/
Submitter: "Zuul (22348)"
Branch: r/stx.5.0
commit 1d7e5be68aa1d8a a167244411d1828 bfc3e3d787
Author: albailey <email address hidden>
Date: Thu Apr 22 18:15:01 2021 -0500
Add missing debug logger entries for VIM
The debug loggers are pre-created during process startup,
and any that are missing can be created using lazy init.
However the lazy init is not multi process safe and can
lead to a subprocess deadlock during the import phase, which
produces no logs or evidence that the thread is stalled.
The workaround at the moment is to ensure that all the debug
loggers defined at import time are configured to be setup when
the process is created.
There is still another cause of a stall. A separate commit
will address it.
Partial-Bug: 1925697 34ab8a1496236a7 8b01a04d51a dbf86620193020b e30bde33d6)
Signed-off-by: albailey <email address hidden>
Change-Id: I90436c1bd063a6
(cherry picked from commit 4ffec12dc88cf43