Add prepareSnapshot method to avoid doing this implicitly in _getOptimes mutex

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Blocker - P1
    • 3.6.0-rc4
    • Affects Version/s: None
    • Component/s: Storage
    • None
    • Fully Compatible
    • ALL
    • Storage 2017-11-13
    • 0
    • None
    • 0
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Instead of unconditionally establishing a snapshot right away when beginning a UnitOfWork, only do this when acquiring a new optime. This keeps the transaction lifetime as short as possible and should fix BF-7113, while still avoiding starting transactions inside of the _getNextOpTimes mutex.

              Assignee:
              Geert Bosch
              Reporter:
              Geert Bosch
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: