Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 8.1.0-rc0
Affects Version/s: None
Component/s: None
Labels:
- auto-reverted

Assigned Teams:

Query Optimization
Backwards Compatibility:
Fully Compatible
Backport Requested:

v8.0, v7.0
Case:
Linked BF Score:
0
Confidence Status:
None
Work Order:
3

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

To make investigating crashes easier, we should improve mongod's signal handler to also print out the current thread's command object (if there is one) along with the stacktrace.

That way, when we have a mongod crash in the future that we want to investigate, we will be able to quickly determine what query was running when the crash happened.

is related to

SERVER-90282 Add more diagnostics to tassert failures

Closed

SERVER-92764 Extend diagnostic logging on tassert failure to dump contents of CurOp/OpDebug

Closed

SERVER-92767 Extend diagnostic logging on tassert failure to apply to additional commands

Closed

SERVER-93194 Extend tassert diagnostic logging to include catalog information

Closed

SERVER-93196 Extend tassert diagnostic logging to include plan cache information

Closed

related to

SERVER-96564 Extend diagnostic logging in tassert/invariant/signal handling to apply to additional commands

Closed

(1 related to)

Assignee:: Hana Pearlman
Reporter:: Drew Paroski
Participants:: David Storch, Drew Paroski, Githook User, Hana Pearlman, Mihai Andrei
Votes:: 6 Vote for this issue
Watchers:: 21 Start watching this issue

Created:: Jun 19 2024 01:45:58 PM UTC
Updated:: Apr 10 2025 01:23:28 PM UTC
Resolved:: Nov 14 2024 01:13:59 PM UTC
Confidence Status Last Update:: 13/Nov/24 3:41 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates