[SERVER-79179] Make create collection coordinator accept a shard parameter Created: 21/Jul/23  Updated: 29/Oct/23  Resolved: 03/Aug/23

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

Type: Task Priority: Major - P3
Reporter: Marcos José Grillo Ramirez Assignee: Marcos José Grillo Ramirez
Resolution: Fixed Votes: 0
Labels: PM-3364-Milestone-1
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-79177 Create a new test cluster command to ... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2023-08-07
Participants:

 Description   

After SERVER-78763 the create collection coordinator will able to create non splittable collections, however, we need to be able to create collections in a shard different than the primary shard. We probably need to create a new split policy, or modify an existing one for this.



 Comments   
Comment by Githook User [ 11/Aug/23 ]

Author:

{'name': 'Marcos José Grillo Ramirez', 'email': 'marcos.grillo@mongodb.com', 'username': 'm4nti5'}

Message: SERVER-79179 Remove unnecessary code in initial split policy
Branch: master
https://github.com/mongodb/mongo/commit/2748da34e6acafcb341f5bc99c758486fc468532

Comment by Githook User [ 07/Aug/23 ]

Author:

{'name': 'Marcos José Grillo Ramirez', 'email': 'marcos.grillo@mongodb.com', 'username': 'm4nti5'}

Message: SERVER-79179 Allow creation of collection in a different shard than the db's primary shard
Branch: minh.luu-no_compile_sys-perf
https://github.com/mongodb/mongo/commit/b4a8ce1d8149c4a1ca3cf5efc02ca60c2b40e8b7

Comment by Githook User [ 03/Aug/23 ]

Author:

{'name': 'Marcos José Grillo Ramirez', 'email': 'marcos.grillo@mongodb.com', 'username': 'm4nti5'}

Message: SERVER-79179 Allow creation of collection in a different shard than the db's primary shard
Branch: master
https://github.com/mongodb/mongo/commit/b4a8ce1d8149c4a1ca3cf5efc02ca60c2b40e8b7

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