[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: |
|
||||||||||||||||||||
| 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. |