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

Cache transaction progress in the Session object

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 3.6.0-rc0
    • None
    • Sharding
    • None
    • Fully Compatible
    • Sharding 2017-10-02
    • 0

    Description

      Currently, checking for whether a write operation already executed is done by traversing the transaction's oplog chain. This is very inefficient because it has to be done for every single write operation in order to even find out whether it needs to be retried or not.

      In order to optimize this we will keep a cache of the last transaction's executed statements so they can be quickly checked.

      Attachments

        Activity

          People

            kaloian.manassiev@mongodb.com Kaloian Manassiev
            kaloian.manassiev@mongodb.com Kaloian Manassiev
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: