[SERVER-38832] Allow a transaction to be prepared behind the read timestamp of storage transactions with ignore_prepared=true Created: 03/Jan/19  Updated: 27/Oct/23  Resolved: 16/Jan/19

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Judah Schvimer Assignee: Judah Schvimer
Resolution: Works as Designed Votes: 0
Labels: prepare_basic
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-38499 Preparing transaction fails and trigg... Closed
Participants:

 Description   

We currently have an invariant that a transaction cannot be prepared behind the read timestamp of another storage transaction. This is fine though if the other storage transaction has "ignore_prepared = true". We need to relax this invariant. If we cannot relax it based on the "ignore_prepared" value of other storage transactions, we may need to consider fully removing the invariant.



 Comments   
Comment by Judah Schvimer [ 16/Jan/19 ]

This shouldn't be necessary anymore per discussion on SERVER-38499.

Comment by Judah Schvimer [ 07/Jan/19 ]

tess.avitabile, good catch! Fixed!

Comment by Tess Avitabile (Inactive) [ 04/Jan/19 ]

I think this should be "Allow a transaction to be prepared behind the read timestamp of storage transactions with ignore_prepared=true".

Generated at Thu Feb 08 04:50:11 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.