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

Change capped collection age-out to be based on collection storageSize, not dataSize

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Works as Designed
    • None
    • None
    • Replication, Storage
    • None
    • ALL

    Description

      Due to SERVER-35431, the dataSize reported for a collection can be incorrect in 4.0, even without unclean crashes. We should switch capped collection sizes to be based on the storageSize, not the dataSize, so that the calculations can be accurate. We also believe this is more likely to be what users actually want when they configure a capped collection anyway, as they are generally trying to limit the disk space consumed by the collection.

      Attachments

        Issue Links

          Activity

            People

              backlog-server-execution Backlog - Storage Execution Team
              spencer@mongodb.com Spencer Brody (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: