[SERVER-55121] The db version is not checked on shard collection's legacy path Created: 10/Mar/21  Updated: 29/Oct/23  Resolved: 19/Mar/21

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

Type: Bug Priority: Major - P3
Reporter: Marcos José Grillo Ramirez Assignee: Marcos José Grillo Ramirez
Resolution: Fixed Votes: 0
Labels: PM-1965-Milestone-1, neweng, sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2021-03-22
Participants:
Linked BF Score: 135

 Description   

When sharding a collection on the legacy path we check if the shard is the database's primary shard however, this check should be done after checking the database version is up to date, like on the DDL coordinator. There is a complication though, on the multiversion suites, we might have a router on last stable that will send the command through the config server, and this will send the command to the shard without attaching the db version, so, doing this check this way, would cause a compatibility issue with older versions. We should check for the db version only if the request came from a router with the latest version.



 Comments   
Comment by Githook User [ 19/Mar/21 ]

Author:

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

Message: SERVER-55121 Check db version on shard collection legacy path

... only if the request came from a router
Branch: master
https://github.com/mongodb/mongo/commit/be9e48ca06057da3aaeb776cd643cb1a1fc910d4

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