[SERVER-54788] Hold the ShardingRoutingInfoFormatStability distLock in setFCV command until the shards have fully upgraded Created: 25/Feb/21  Updated: 29/Oct/23  Resolved: 25/Feb/21

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

Type: Task Priority: Major - P3
Reporter: Jordi Serra Torrens Assignee: Jordi Serra Torrens
Resolution: Fixed Votes: 0
Labels: PM-1965-Milestone-0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Participants:

 Description   

The scope during which we hold the ShardingRoutingInfoFormatStability during FCV upgrade is too narrow. We should actually hold it until the shards have fully upgraded so that, for example, a shardCollection does not write old metadata after the configsvr has patched up the metadata.



 Comments   
Comment by Githook User [ 25/Feb/21 ]

Author:

{'name': 'Jordi Serra Torrens', 'email': 'jordi.serra-torrens@mongodb.com', 'username': 'jordist'}

Message: SERVER-54788: Hold the ShardingRoutingInfoFormatStability distLock in setFCV command until the shards have fully upgraded
Branch: master
https://github.com/mongodb/mongo/commit/3a71f0a8f695e974dfe383fbcfebb69f5985761c

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