waitUntilDurable() should use its own WT_SESSION, not one from the cache

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major - P3
    • 3.6.0-rc4
    • Affects Version/s: None
    • Component/s: Storage
    • None
    • Fully Compatible
    • Storage 2017-11-13
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      waitUntilDurable() only needs a session to call log_flush() and checkpoint(). Since it uses no cursors, it should be fine to have it simply use one long-lived session object for this, rather than getting a session out of the cache every time.
      The benefit for this will be to reduce contention on the mutex that protects the session cache, as it must be locked every time a session is taken out of the cache and every time a session is returned to the cache.

            Assignee:
            Eric Milkie
            Reporter:
            Eric Milkie
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: