-
Type: Improvement
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
Fully Compatible
-
Repl 2018-08-27, Repl 2018-09-10
It is important that this oplog entry either always happens after the prepareTransaction oplog entry, or that them being out of order is safe. It is fine if there is an abort oplog entry with no corresponding prepare oplog entry.
- is depended on by
-
SERVER-32324 Update transaction table when an abortTransaction oplog entry is written
- Closed
-
SERVER-35875 Secondaries abort transactions when applying abortTransaction oplog entries
- Closed
- is duplicated by
-
SERVER-35669 Write an abortTransaction oplog entry any time a transaction that went into the "preparing" state aborts
- Closed
- is related to
-
SERVER-76741 Split-prepare transactions are aborted before reserving abort oplog entry
- Closed
- related to
-
SERVER-35430 Abort a transaction if prepare fails
- Closed