Loading...

XML

Word

Printable

JSON

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

Assigned Teams:

Query Optimization
Backwards Compatibility:
Fully Compatible
Backport Requested:

v8.0, v7.0
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

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

A tassert failure currently only logs a stacktrace and error code. It would be useful for diagnostic purposes to include more information to allow easier reproduction of bugs. For example, the current command in its entirety, the state of the catalog, and plan cache.

is duplicated by

SERVER-90404 Include additional diagnostic into tassert

Closed

is related to

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-91686 Improve mongod's signal handler to print out current thread's command object

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

(1 related to)

Assignee:: Ben Shteinfeld
Reporter:: Ben Shteinfeld
Participants:: Ben Shteinfeld, Githook User
Votes:: 1 Vote for this issue
Watchers:: 14 Start watching this issue

Created:: May 07 2024 03:08:24 PM UTC
Updated:: Jan 08 2025 07:15:21 PM UTC
Resolved:: Jul 24 2024 09:18:24 PM UTC
Confidence Status Last Update:: 10/May/24 3:00 PM

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates