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

Add a no-op oplog entry for shardCollection command

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 6.0.0-rc0
    • None
    • None
    • Fully Compatible
    • QE 2022-02-07, QE 2022-02-21, QE 2022-03-07

    Description

      As a part of the PM-1950 shardCollection will generate an entry in the oplog on the primary shard. The oplog entry will use the “no-op” type. This way,it is still going to be replicated, but result in no work being done by secondaries as part of oplog application (even in older versions of MongoDB). Writing this no-op entry should happen before deleting the state document corresponding to the operation.

      Attachments

        Activity

          People

            misha.tyulenev@mongodb.com Misha Tyulenev
            nikita.lapkov@mongodb.com Nikita Lapkov (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: