-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Replication
-
Fully Compatible
-
Repl 2023-07-24, Repl 2023-08-07, Repl 2023-08-21, Repl 2023-09-04, Repl 2023-09-18, Repl 2023-10-02
-
135
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.
- is related to
-
SERVER-79164 Investigate how to improve diagnosability of write conflicts
- Open
- related to
-
SERVER-76741 Split-prepare transactions are aborted before reserving abort oplog entry
- Closed
-
SERVER-79033 Image collection invalidation for missing namespace during initial sync always attempts upsert
- Closed
-
SERVER-76299 Report writeConflicts in serverStatus on secondaries
- Closed