-
Type:
Improvement
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Fully Compatible
-
Service Arch 2022-05-16, Service Arch 2022-05-30
-
135
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
ThreadName is a low-level diagnostic, not a db business object.
For maximum generality, it should not have any idea what mongodb is.
The idea that there's a "pre-init" for ThreadName, or that it depends on a MONGO_INITIALIZER for ThreadContext to get started is a bad fit that
causes bugs: SERVER-58194, SERVER-63852.
After working on ThreadName's API I don't see a reason for it to be connected to ThreadContext.
- is depended on by
-
SERVER-66455 Undo ~OpMsgFuzzerFixture fix
-
- Closed
-
-
-
- Closed
-
- related to
-
-
- Open
-
-
-
- Closed
-
-
-
- Closed
-
- split from
-
-
- Closed
-