[SERVER-54355] New createCollection coordinator unconditionally create initial chunks with collection UUID Created: 05/Feb/21  Updated: 27/Oct/23  Resolved: 03/Mar/21

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: Backlog
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Tommaso Tocci Assignee: [DO NOT USE] Backlog - Sharding EMEA
Resolution: Works as Designed Votes: 0
Labels: PM-1965-Milestone-0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
is caused by SERVER-52779 Implement the new create/shard collec... Closed
Assigned Teams:
Sharding EMEA
Operating System: ALL
Steps To Reproduce:

Run jstests/sharding/basic_drop_coll.js with featureFlagShardingFullDDLSupport enabled and featureFlagShardingFullDDLSupportTimestampedVersion disabled

Participants:

 Description   

If the shardingFullDDLSupportTimestampedVersion feature flags is enable the chunks in config.chunks are indexed by and contains the UUID of the collection. While the legacy createCollection code takes this into account, the new createCollection coordinator doesn't check for this feature flags and unconditionally attach the UUID fields to the initial chunks

We didn't spot this bug till now because we either test with all the feature flags enable or with all of them disable.



 Comments   
Comment by Kaloian Manassiev [ 03/Mar/21 ]

It is the intention that the new DDL coordinator will only know about the new format.

Generated at Thu Feb 08 05:33:18 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.