Capped Collection size should account for Data + Index

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Storage
    • None
    • Storage Execution
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Currently capped collection size does not account for index size. This can lead to situations where a capped collection fits the volume it is on, but the additional space required by the indexes causes it to exceed the capacity of the volume. See related ticket : SERVER-21895

              Assignee:
              [DO NOT USE] Backlog - Storage Execution Team
              Reporter:
              Angshuman Bagchi (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: