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

Investigate using ranged truncation for capped collection deletion

    • Type: Icon: Task Task
    • Resolution: Won't Do
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Storage
    • None
    • Storage Execution

      SERVER-55156 removes the capped collection truncation optimization here in an effort to simplify the work needed for SERVER-16049. Using a ranged truncation may prove useful for workloads where the insertion of one document requires the deletion of multiple documents.

      A few things that we'd need to make this a reality that came to mind:

      • Implement a new record store function to do ranged truncation on a collection.
        • Similiar to cappedTruncateAfter().
      • Create a new oplog entry type for replicating these truncation operations.

            Assignee:
            backlog-server-execution [DO NOT USE] Backlog - Storage Execution Team
            Reporter:
            gregory.wlodarek@mongodb.com Gregory Wlodarek
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: