[SERVER-79159] Track unsharded collections on upgrade Created: 20/Jul/23  Updated: 07/Feb/24

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

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

Issue Links:
Depends
depends on SERVER-84153 Sharded cluster fixture set up does n... Closed
depends on SERVER-80372 Make implicit collection creation cal... Closed
depends on SERVER-81189 Transform `create` requests in sharde... Closed
is depended on by SERVER-83214 Handle direct connection database and... Backlog
is depended on by SERVER-83226 Handle direct connection database and... Backlog
Related
related to SERVER-83791 Rename collection should track collec... Open
Assigned Teams:
Sharding EMEA
Sprint: Sharding EMEA 2023-10-02, Sharding EMEA 2023-10-16, CAR Team 2023-11-27, CAR Team 2023-12-11, CAR Team 2023-12-25, CAR Team 2024-01-08, CAR Team 2024-01-22, CAR Team 2024-02-05
Participants:

 Description   

Besides making the createCollection path to commit the collection metadata in the config server for unsharded collections, we need to make sure that:

  • When running FCV from 8.0 to 8.1 in a fully upgraded sharded cluster, all unsharded collections on all shards must be tracked

Additionally, we need to ensure that all DDL are properly feature flagged and drained if necessary.



 Comments   
Comment by Marcos José Grillo Ramirez [ 13/Dec/23 ]

Found a dependency that should be committed before this ticket: SERVER-84153

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