[SERVER-34954] Verify unique index version upgrade for new --shardsvr nodes added to FCV 4.2 replica set shards Created: 11/May/18  Updated: 29/Oct/23  Resolved: 09/Aug/18

Status: Closed
Project: Core Server
Component/s: Upgrade/Downgrade
Affects Version/s: None
Fix Version/s: 4.1.2

Type: Task Priority: Major - P3
Reporter: Maria van Keulen Assignee: Sulabh Mahajan
Resolution: Fixed Votes: 0
Labels: nonnyc, storage-engines
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-32825 Add the infrastructure for upgrade/do... Closed
depends on SERVER-34489 Enable new format Unique Index via FCV Closed
Backwards Compatibility: Fully Compatible
Sprint: Storage Engines 2018-07-30, Storage Engines 2018-08-13
Participants:

 Description   

In 3.6, this test was added as part of SERVER-32255 to ensure a 3.6 node started with the shardsvr option (hence, with FCV initially set to 3.4) and added to an FCV 3.6 replica set shard would correctly get UUIDs added to nonreplicated collections during initial sync. A similar test should be created to test the unique index upgrade work for 4.2.



 Comments   
Comment by Githook User [ 09/Aug/18 ]

Author:

{'name': 'Sulabh Mahajan', 'email': 'sulabh.mahajan@mongodb.com', 'username': 'sulabhM'}

Message: SERVER-34954 Add test to check unique indexes on a newly added --shardsvr node
Branch: master
https://github.com/mongodb/mongo/commit/0dea042ec8d7bf8e0548f9bb5dc149febf6cb82e

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