Allow a transaction to be prepared behind the read timestamp of storage transactions with ignore_prepared=true

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Works as Designed
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Storage
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            Judah Schvimer
            Reporter:
            Judah Schvimer
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: