[SERVER-48202] Test printStackTrace on initialization Created: 13/May/20  Updated: 06/Dec/22

Status: Backlog
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Amirsaman Memaripour Assignee: Backlog - Service Architecture
Resolution: Unresolved Votes: 0
Labels: sa-remove-fv-backlog-22
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Gantt Dependency
has to be done after SERVER-49110 Fix symbol collection errors for libu... Closed
has to be done after SERVER-46726 Provide separate setParameter to disa... Closed
Related
is related to SERVER-47775 LOGV2_FATAL failed to print stack trace Closed
Assigned Teams:
Service Arch
Sprint: 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
Participants:

 Description   

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.


Generated at Thu Feb 08 05:16:26 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.