-
Type: Task
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Server Programmability
-
Service arch 2020-05-18, Service arch 2020-06-01, Service arch 2020-06-15, Service arch 2020-06-29, Service arch 2020-07-13
We should verify that printStackTrace() can walk the stack and collect the required information at startup (e.g., by defining a MONGO_INITIALIZER and printing the stack-trace to void).
On failure, we should log the incident at Warning level. With test commands enabled, the severity should be increased to Fatal.
- has to be done after
-
SERVER-49110 Fix symbol collection errors for libunwind
- Closed
-
SERVER-46726 Provide separate setParameter to disable diagnostic work
- Closed
- is related to
-
SERVER-47775 LOGV2_FATAL failed to print stack trace
- Closed