Cache transaction progress in the Session object

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major - P3
    • 3.6.0-rc0
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Fully Compatible
    • Sharding 2017-10-02
    • 0
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            Kaloian Manassiev
            Reporter:
            Kaloian Manassiev
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: