batchSize:0 snapshot reads must allocate a WiredTiger transaction

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 3.7.4
    • Affects Version/s: None
    • Component/s: Storage
    • None
    • Fully Compatible
    • Storage NYC 2018-03-26, Storage NYC 2018-03-12
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      We currently open WiredTiger transactions in a lazy manner. As batchSize:0 reads do not need to access collection data, we do not start a WiredTiger transaction until the subsequent getMore.

      For readConcern level snapshot reads this is counter-intuitive and allows for reading of writes that occur in-between the find and getMore.

            Assignee:
            James Wahlin
            Reporter:
            James Wahlin
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: