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

Writes done as part of movePrimary should not generate change stream events

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Cluster Scalability

      Both the cloning of the data (recipient side) and the purging of stale data (donor side) of the the movePrimary command generate useless change stream events.

      The generation of these events on cloning phase could be addressed in the context of the Online movePrimary project (PM-3025), while these on cleaning stale data in the context of making the movePrimary command resilient.

            Assignee:
            backlog-server-cluster-scalability [DO NOT USE] Backlog - Cluster Scalability
            Reporter:
            antonio.fuschetto@mongodb.com Antonio Fuschetto
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: