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

ScopedCollectionDescription shouldn't hold a RangePreserver

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 7.1.0-rc0, 7.0.2
    • Affects Version/s: 7.1.0-rc0
    • Component/s: None
    • None
    • Sharding EMEA
    • Fully Compatible
    • ALL
    • v7.0
    • Sharding EMEA 2023-08-21, Sharding EMEA 2023-09-04
    • 119

      `ScopedCollectionDescription` is currently holding a RangePreserver that blocks orphans from being deleted. This is because calling `_getCurrentMetadataIfKnown` with boost::none argument will always attach a RangePreserver.
      ScopedCollectionDescription is not an orphan filter, therefore it does not require this range-preserving property.

            Assignee:
            allison.easton@mongodb.com Allison Easton
            Reporter:
            jordi.serra-torrens@mongodb.com Jordi Serra Torrens
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: