The commit of createCollection should not generate op entries related to shardCollection

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 7.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • CAR Team 2023-12-25
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      SERVER-81188 introduced a common execution path for the createCollection and shardCollection user requests through the CreateCollectionCoordinator, which includes logic (based on the notifyChangeStreamsOnShardCollection method) that generated no-op entries on the oplog of the primary shard when the request is committed.

      Nevertheless, such op entries are only meant to serve the shardCollection path - and should not be generated under different scenarios.

            Assignee:
            Paolo Polato
            Reporter:
            Paolo Polato
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: