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

listCollections can return empty metadata for a collection which has been concurrently dropped

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 5.1.0, 5.0.0-rc0
    • Component/s: None
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v5.0
    • Sprint:
      Execution Team 2021-05-17, Execution Team 2021-05-31
    • Linked BF Score:
      158

      Description

      This is very similar to SERVER-56002, whereby a lock-free operation attempts to access the DurableCatalog while a concurrent operation is modifying it. For listCollections, its possible to lookup the collection in the CollectionCatalog just before a collection has been dropped, which means it no longer has an entry in the DurableCatalog. Then, when listCollections proceeds to read the collection options, it receives an empty object and returns it in the command response.

      One possible downstream impact for this is a failed shardCollection command when try to extract the UUID of the collection to shard.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              henrik.edin Henrik Edin
              Reporter:
              nicholas.zolnierz Nicholas Zolnierz
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: