[SERVER-84048] The commit of createCollection should not generate op entries related to shardCollection Created: 11/Dec/23  Updated: 18/Dec/23  Resolved: 18/Dec/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.3.0-rc0

Type: Task Priority: Major - P3
Reporter: Paolo Polato Assignee: Paolo Polato
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: CAR Team 2023-12-25
Participants:

 Description   

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.



 Comments   
Comment by Githook User [ 15/Dec/23 ]

Author:

{'name': 'Paolo Polato', 'email': 'paolo.polato@mongodb.com', 'username': 'ppolato'}

Message: SERVER-84048 Do not generate shardCollection op entry when committing unsplittable collections

GitOrigin-RevId: 6ab32434efb5551ad8c8ce2a356da4dc8108936b
Branch: master
https://github.com/mongodb/mongo/commit/8165932961f4924bdfe1c2e1119fca5908a3efa5

Generated at Thu Feb 08 06:53:54 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.