[SERVER-51816] Make `renameCollection` in a cluster pass through the config server Created: 23/Oct/20  Updated: 04/Nov/20  Resolved: 04/Nov/20

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

Type: Task Priority: Major - P3
Reporter: Pierlauro Sciarelli Assignee: Pierlauro Sciarelli
Resolution: Won't Do Votes: 0
Labels: PM-1965-Milestone-0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Sprint: Sharding 2020-11-02, Sharding 2020-11-16
Participants:

 Description   

Currently, the rename collection command is being directly routed to just one shard, namely the db's primary shard since it just accounts for unsharded collections.

Aim of this ticket is just to add an additional hop (router -> config server -> primary shard). As part of PM-1965, DDL commands are expected to pass by the CSRS in order to choose which code path to follow based on the FVC status.



 Comments   
Comment by Pierlauro Sciarelli [ 04/Nov/20 ]

Closing as won't do because it was decided to implement 2-phase FCV, that will allow to directly target shards for renameCollection.

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