Loading...

XML

Word

Printable

JSON

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

Backwards Compatibility:
Fully Compatible
Sprint:
Repl 2019-01-28, Repl 2019-02-11, Repl 2019-02-25, Repl 2019-03-11
Linked BF Score:
10

Multi-document transactions with read concern level local or majority perform a timestamped read at the lastApplied. Since the lastApplied is ahead of the all-committed, after the work to allow WT read at a timestamp without a snapshot, this could cause these transactions to read uncommitted storage transactions. It is essential that multi-document transactions with read concern level local read at lastApplied, so that w:1 writes are visible to these transactions. As a solution, multi-document transactions reading ahead of all-committed will not perform a timestamped read.

has to be done before

SERVER-40145 Re-enable test suites that exercise overlapping prepared and read timestamps

Closed

is depended on by

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

Closed

is related to

SERVER-34837 Make the default readConcern level for transactions be speculative majority

Backlog

related to

SERVER-40352 Transactions that perform untimestamped reads do not check min visible snapshot for collection

Closed

SERVER-39364 Audit uses of setLastOpToSystemLastOpTime

Closed

SERVER-69478 remove unnecessary copy in TransactionParticipant::commitUnpreparedTransaction()

Closed

links to

Proposals for avoiding timestamp reads ahead of all-committed

(1 related to, 1 links to)

Assignee:: A. Jesse Jiryu Davis

Reporter:: Tess Avitabile (Inactive)

Participants:: A. Jesse Jiryu Davis, Andy Schwerin, Daniel Gottlieb, Githook User, Judah Schvimer, Tess Avitabile

Votes:: 0 Vote for this issue

Watchers:: 11 Start watching this issue

Created:: Jan 09 2019 02:28:05 PM UTC

Updated:: Oct 29 2023 10:25:18 PM UTC

Resolved:: Feb 22 2019 01:08:55 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates