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

WiredTigerSessionCache does not properly dispose of sessions released after rollback

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.1.0-rc0
    • Affects Version/s: 7.0.6, 5.0.25, 6.0.14, 8.0.0
    • Component/s: None
    • None
    • Storage Execution
    • Fully Compatible
    • ALL
    • v8.0, v7.0, v6.0, v5.0
    • Execution Team 2024-09-02, Execution Team 2024-10-14, Execution Team 2024-10-28, Execution Team 2024-11-11
    • 200

      We don’t release cursors if the WiredTigerSessionCache is shutting down (in rollback).

      But then when the session gets released after rollback, and the session cache is no longer shutting down, we try to release a session with cursors that aren't closed.

      This triggers an invariant that cursors must be all closed before releasing the session back into the cache.

            Assignee:
            damian.wasilewicz@mongodb.com Damian Wasilewicz
            Reporter:
            louis.williams@mongodb.com Louis Williams
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: