Investigate changes in SERVER-78665: Implement replicated truncates for internal clustered collections

    • Type: Investigation
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Tools and Replicator
    • 1

      Original Downstream Change Summary

      This change introduces a new oplog command entry sub-type truncateRange.
      Tools or applications that read the oplog collection directly need to be prepared to handle or ignore this new oplog command.

      Tools or applications that consume the oplog via change streams are not affected, because the truncateRange oplog commands will not be emitted as change events.

      Description of Linked Ticket

      Implement replicated truncates API. Follow up work will use this API to truncate the change streams pre-image collection and the oplog collection. Fast, general data deletion will be worked on in SPM-3939

       

      There are some use-cases where truncating the contents of a collection makes sense. This today is being done by performing a coll.deleteMany without a filter, resulting in multiple oplog delete entries being created/replicated and taking a long time to process.

      Performing a truncate on a collection would delete the contents of a collection plus all indexes in this situation.

            Assignee:
            Unassigned
            Reporter:
            Backlog - Core Eng Program Management Team
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: