[SERVER-76774] Invariant that secondary oplog application doesn't get prepare conflicts Created: 02/May/23  Updated: 29/Oct/23  Resolved: 18/Sep/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.2.0-rc0

Type: Task Priority: Major - P3
Reporter: Lingzhi Deng Assignee: Jiawei Yang
Resolution: Fixed Votes: 0
Labels: repl-shortlist
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-76741 Split-prepare transactions are aborte... Closed
related to SERVER-79033 Image collection invalidation for mis... Closed
related to SERVER-76299 Report writeConflicts in serverStatus... Closed
is related to SERVER-79164 Investigate how to improve diagnosabi... Open
Assigned Teams:
Replication
Backwards Compatibility: Fully Compatible
Sprint: Repl 2023-07-24, Repl 2023-08-07, Repl 2023-08-21, Repl 2023-09-04, Repl 2023-09-18, Repl 2023-10-02
Participants:
Linked BF Score: 135

 Description   

Alternatively, maybe we should crash the server if secondary oplog application repeatedly get write conflicts for some time as WiredTiger will map all the WT_PREPARE_CONFLICT errors to WT_ROLLBACK (aka write conflicts) for write operations.

We may want to add the invariant / the crashing behavior only in testing, not in production.



 Comments   
Comment by Githook User [ 18/Sep/23 ]

Author:

{'name': 'Jiawei Yang', 'email': 'jiawei.yang@mongodb.com', 'username': 'YoungYang0820'}

Message: SERVER-76774 fassert in secondary oplog application prepare conflicts in tests
Branch: master
https://github.com/mongodb/mongo/commit/1ff1494d992f300bb150684a2fa6cefe3348d1cf

Generated at Thu Feb 08 06:33:34 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.