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

Asserting that no cursor is active when resetting a WT session

    • Type: Icon: Improvement Improvement
    • Resolution: Won't Do
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • Execution Team 2024-09-02

      In BF-33263 we have two index scans. If one plan happens to yield, it calls abandonSnapshot() which by default does a WT rollback_transaction and resets all positioned cursors. The other plan is now using an invalid cursor. This bug only manifests probabilistically unless internalQueryExecYieldIterations is set to 1 and is only caught by ASAN.

            Assignee:
            wei.hu@mongodb.com Wei Hu
            Reporter:
            wei.hu@mongodb.com Wei Hu
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: