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

Evaluate doing batched capped deletes in CollectionImpl::_cappedDeleteAsNeeded

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution

      Currently, deleting documents in '_cappedDeleteAsNeeded' happens in one transaction. As a result of SERVER-1864, this could be costly in the case where the newly set cappedSize decreases past the collections current size.

      SERVER-1864 holds off on deleting documents until the next insert into the collection. After inserting, we check if deletions are needed and delete documents until the total size < cappedSize in one transaction. 

            Assignee:
            backlog-server-execution [DO NOT USE] Backlog - Storage Execution Team
            Reporter:
            fausto.leyva@mongodb.com Fausto Leyva (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: