Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 8.2.0-rc0, 8.1.2
Affects Version/s: None
Component/s: None
Labels:
- neweng
- reliability-sno

Assigned Teams:

Networking & Observability
Backwards Compatibility:
Fully Compatible
Backport Requested:

v8.1, v8.0, v7.0
Sprint:
N&O 2025-06-09, N&O 2025-06-23
Linked BF Score:
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

Investigate if it is possible to identify which server status section threw an exception in the FTDC doLoop() function. This would be very useful for identifying crashes in the FTDC thread.

is depended on by

SERVER-101459 MongoDB service went down due to an error - BSONObjectTooLarge

Backlog

related to

SERVER-101459 MongoDB service went down due to an error - BSONObjectTooLarge

Backlog

SERVER-106302 Provide visibility if aggregate FTDC object is too large

Open

Assignee:: Michael Popov
Reporter:: Erin McNulty
Participants:: Erin McNulty, Githook User, Michael Popov
Votes:: 0 Vote for this issue
Watchers:: 4 Start watching this issue

Created:: Nov 25 2024 10:08:59 PM UTC
Updated:: Jun 20 2025 03:03:46 PM UTC
Resolved:: Jun 13 2025 04:34:57 AM UTC

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates