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

Out-of-order destruction of AutoGet* objects can lead to transaction closure

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 5.0.0-rc0
    • None
    • None
    • None
    • Fully Compatible
    • ALL
    • Query Execution 2021-04-19
    • 166

    Description

      Steps to reproduce:

      1. AutoGetCollectionForReadMaybeLockFree number one is created
      2. AutoGetCollectionForReadMaybeLockFree number two is created
      3. We destroy the first object
      4. Deep underneath this object holds GlobalLock, which thinks it is outermost, since it was created first
      5. GlobalLock calls abandonSnapshot(), closing transaction and reseting the cursors

      Attachments

        Activity

          People

            mihai.andrei@mongodb.com Mihai Andrei
            nikita.lapkov@mongodb.com Nikita Lapkov (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: