db storage size not reducing after range deletion

XMLWordPrintableJSON

    • Storage Engines, Storage Engines - Persistence
    • StorEng - Defined Pipeline, StorEng - 2024-10-29, StorEng - 2024-11-12
    • None

      I have a sharded cluster where I moved my entire collection from shard0 to shard1 and range deletion completed but the db storage size remains the same. No space has been reclaimed. Attaching a screenshot of Atlas storage size metrics 

      • why does this happen?
      • is this a start of time problem? 

            Assignee:
            Sean Watt
            Reporter:
            Ratika Gandhi
            Votes:
            0 Vote for this issue
            Watchers:
            14 Start watching this issue

              Created:
              Updated:
              Resolved: