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

listIndexes can read partial state from renameCollection

    XMLWordPrintableJSON

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

          is depended on by

          Task - A task that needs to be done. SERVER-52713 [testing] Add stepdown/kill/terminate to tenant_migration_jscore_passthrough

          • Major - P3 - Major loss of function.
          • Closed
          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. SERVER-55519 Investigate missing _id index during collection cloning in tenant migration

          • Major - P3 - Major loss of function.
          • Closed
          is related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-55519 Investigate missing _id index during collection cloning in tenant migration

          • Major - P3 - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. SERVER-56023 listCollections can return empty metadata for a collection which has been concurrently dropped

          • Major - P3 - Major loss of function.
          • Closed
          related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-56877 insert operations may fail to set index to multikey after aborted multikey catalog update

          • Major - P3 - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. SERVER-57083 Coverity analysis defect 120111: Parse warning

          • Major - P3 - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. SERVER-57324 dropDatabase should not modify CollectionCatalog inplace

          • Major - P3 - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. SERVER-57775 collection metadata for multikey not removed after WriteConflictException from durable catalog update

          • Major - P3 - Major loss of function.
          • Closed

          Task - A task that needs to be done. SERVER-57127 Refactor multikey and other state out of IndexCatalogEntry

          • Major - P3 - Major loss of function.
          • Closed

          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: