[SERVER-41185] Make ftdc failures process fatal Created: 16/May/19  Updated: 29/Oct/23  Resolved: 19/Nov/19

Status: Closed
Project: Core Server
Component/s: Internal Code
Affects Version/s: None
Fix Version/s: 4.3.1

Type: New Feature Priority: Major - P3
Reporter: Mira Carey Assignee: Mark Benvenuto
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by DOCS-15178 [Server] The fact that failure to cre... Closed
Problem/Incident
Related
is related to SERVER-75601 Make serverStatus apiversion field mo... Closed
Backwards Compatibility: Fully Compatible
Sprint: Dev Tools 2019-08-26, Dev Tools 2019-09-09, Dev Tools 2019-09-23, Dev Tools 2019-10-07, Dev Tools 2019-10-21, Security 2019-11-18, Security 2019-12-02
Participants:
Case:

 Description   

When we first introduced full time data capture, it was written to avoid damaging the parent process if it all possible. In the interest of achieving that aim, certain failures cause ftdc to halt itself, rather than retry or terminate the process.

However, over the years we've come to rely more and more on the diagnostics ftdc provides. We've also seen few to no instances of ftdc taking down an otherwise healthy node.

Making ftdc failures terminate the process will reduce the number of cases where a moment of resource exhaustion (say in file descriptors) causes ftdc to unload, after which we're left with a less than fully operational mongod/s



 Comments   
Comment by Githook User [ 19/Nov/19 ]

Author:

{'username': 'markbenvenuto', 'email': 'mark.benvenuto@mongodb.com', 'name': 'Mark Benvenuto'}

Message: SERVER-41185 Make ftdc failures process fatal
Branch: master
https://github.com/mongodb/mongo/commit/cffaa3c53fa3a404273f767f55f1a93f1320a209

Generated at Thu Feb 08 04:57:02 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.