[SERVER-32613] [placeholder] all operations targeted by primary shard are sent with a database version Created: 09/Jan/18  Updated: 06/Dec/22  Resolved: 08/Mar/18

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

Type: Task Priority: Major - P3
Reporter: Randolph Tan Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Sharding
Participants:

 Description   

The catalog commands are:

  • createCollection (create collection or view)
  • renameCollection
  • shardCollection
  • dropCollection
  • collMod (change collection options)
  • createIndexes
  • dropIndexes

Routing changes:
An explicit createCollection, renameCollection, and dropCollection will always be routed to the config server, since they now always modify the sharding catalog.

collMod, createIndexes, and dropIndexes will have a unified code path between sharded and unsharded collections: they will always be sent to the primary shard (with a database version) plus all shards that own chunks for the collection (with shardVersions).

dropCollection will also have a unified code path between sharded and unsharded, but it will still be broadcast to all shards (since we do not delete catalog data from a donor shard after moving the last chunk off the donor, and we now allow moving unsharded collections).



 Comments   
Comment by Esha Maharishi (Inactive) [ 08/Mar/18 ]

Closing as duplicate since these have been ticketed out individually now.

Generated at Thu Feb 08 04:30:46 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.