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

listIndexes can read partial state from renameCollection

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 5.0.0-rc0, 5.1.0-rc0
    • None
    • None
    • Fully Compatible
    • ALL
    • v5.0
    • Execution Team 2021-05-17, Execution Team 2021-05-31
    • 158

    Description

      Essentially, the issue appears to be that listIndexes can read from the DurableCatalog in the middle of a concurrent collection rename (after the original target was dropped, but before the source collection is renamed). This looks to be possible because the listIndexes can read from the DurableCatalog using the same catalogId that the collection rename removes from the DurableCatalog.

      Some ideas for how to fix this include making listIndexes no longer lock free as well as reimplementing listIndexes to use the IndexCatalog instead of the DurableCatalog.

      Attachments

        Issue Links

          Activity

            People

              henrik.edin@mongodb.com Henrik Edin
              mihai.andrei@mongodb.com Mihai Andrei
              Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: