[SERVER-31605] Un-blacklist cross-version UUID checks Created: 17/Oct/17  Updated: 30/Oct/23  Resolved: 07/Jun/22

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

Type: Improvement Priority: Major - P3
Reporter: Nathan Myers Assignee: Allison Easton
Resolution: Fixed Votes: 0
Labels: UnblacklistTests, shardingemea-qw
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-31191 Store the collection UUIDs in the Cat... Closed
is related to SERVER-32368 do not perform UUID check against a s... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2022-06-13
Participants:
Story Points: 1

 Description   

The resolution for SERVER-31191, aeabbf96ff3c2990f553ba0a5e6e1d18ebddab2f, added a UUID consistency check that had to be blacklisted on mixed-version runs because 3.4 does not maintain UUIDs on its sharded collections.

With a little more finesse, relevant parts of these checks could be restored.



 Comments   
Comment by Githook User [ 07/Jun/22 ]

Author:

{'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}

Message: SERVER-31605 Un-blacklist cross-version UUID checks
Branch: master
https://github.com/mongodb/mongo/commit/96e2dac067cef8e5f0b8b69baf374873a60a3291

Comment by Esha Maharishi (Inactive) [ 17/Oct/17 ]

One solution is to:

  • only persist the routing table cache on shards if in schemaVersion=3.6 (aka, either upgrading to or full in fcv=3.6)
  • drop the persisted routing table cache from shards on fcv downgrade to 3.4
Generated at Thu Feb 08 04:27:37 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.