Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 4.1.3
Affects Version/s: None
Component/s: Replication
Labels:
- prepare_durability

Backwards Compatibility:
Fully Compatible
Sprint:
Repl 2018-08-27, Repl 2018-09-10
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

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

Assignee:: Judah Schvimer
Reporter:: Judah Schvimer
Participants:: Githook User, Judah Schvimer
Votes:: 0 Vote for this issue
Watchers:: 2 Start watching this issue

Created:: Jun 28 2018 03:41:38 PM UTC
Updated:: Oct 29 2023 10:30:18 PM UTC
Resolved:: Sep 07 2018 02:20:56 PM UTC
Confidence Status Last Update:: 09/Aug/18 9:58 PM

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates