[SERVER-59235] Change fassert and invariant to fassertNoTrace when failing to startup Created: 10/Aug/21  Updated: 06/Dec/22

Status: Backlog
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Huayu Ouyang Assignee: Backlog - Replication Team
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Assigned Teams:
Replication
Participants:
Linked BF Score: 6

 Description   

Currently, when we try to restart an empty standalone, it will fail trying to recover, and we fail it with an fatal assertion.

Additionally, when we try to restart a replica set node with the recoverFromOplogAsStandalone parameter set, it also fails. We fail it with an invariant here.

We should consider changing the fassert and invariant to fassertNoTrace to avoid core dumping and stack tracing, since the issue is with the startup parameter/the data the server has been fed, and not an issue with the server logic itself.


Generated at Thu Feb 08 05:46:43 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.