Loading...

XML

Word

Printable

JSON

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

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

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

Other read concern levels already accept that they can see partial transactions.

is depended on by

SERVER-36953 afterClusterTime reads should not block on prepare conflicts if their afterClusterTime is before the oldest prepare timestamp

Closed

related to

SERVER-38499 Preparing transaction fails and triggers invariant if chosen timestamp is not greater than WiredTiger's latest active read timestamp

Closed

Assignee:: Samyukta Lanka
Reporter:: Judah Schvimer
Participants:: Githook User, Gregory McKeon, Judah Schvimer, Samyukta Lanka
Votes:: 0 Vote for this issue
Watchers:: 4 Start watching this issue

Created:: Jul 31 2018 09:51:25 PM UTC
Updated:: Oct 29 2023 10:29:24 PM UTC
Resolved:: Sep 05 2018 06:14:10 PM UTC
Confidence Status Last Update:: 14/Aug/18 8:10 PM