Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-33771

Vectored inserts should not generate optimes for multi-statement transactions

    • Type: Icon: Bug Bug
    • Resolution: Gone away
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Storage
    • None
    • ALL
    • Storage NYC 2018-03-26

      Currently, performing vectored inserts generates OpTimes for every insert operation, which sets the commit_timestamp on the current WiredTiger transaction for every operation here.

      This is problematic because calling prepare_transaction is not possible after a commit timestamp has been set.

      The OpTime should be generated once the transaction commits.

            Assignee:
            louis.williams@mongodb.com Louis Williams
            Reporter:
            louis.williams@mongodb.com Louis Williams
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: