[SERVER-78653] Remove renameCollection static checks from coordinator Created: 04/Jul/23  Updated: 29/Oct/23  Resolved: 06/Jul/23

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

Type: Task Priority: Major - P3
Reporter: Pau Baldillou Salse (Inactive) Assignee: [DO NOT USE] Backlog - Sharding EMEA
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-75357 Consider moving static checks in rena... Closed
Assigned Teams:
Sharding EMEA
Backwards Compatibility: Fully Compatible
Participants:

 Description   

Starting from version 7.1, we moved the renameCollection static checks from the coordinator (primary shard) to the router (SERVER-75357). In order to ensure that those checks would be performed in multiversion scenarios (mongos in v7.0 and mongod in more recent version), they need to be kept in the coordinator until v8.0 has branched out.

When 8.0 becomes LTS, the checks in the primary shard should be removed.


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