[SERVER-47112] Improve setFeatureCompatibilityVersion 4.2 impact with many tables Created: 25/Mar/20  Updated: 06/Dec/22

Status: Backlog
Project: Core Server
Component/s: Replication, Storage
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Dmitry Agranat Assignee: Backlog - Storage Execution Team
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File setFCV.png    
Issue Links:
Related
Assigned Teams:
Storage Execution
Operating System: ALL
Participants:
Case:

 Description   

When a primary executes setFCV("4.2") its main work is to upgrade all its unique indexes to a new format (SERVER-32825). It writes a collMod oplog entry per collection to trigger the secondaries to upgrade their unique indexes too.

When mongos executes setFCV, it sends it to the primary of the config replica set, which sends it to the primary of each shard, and waits for majority acknowledgement.



 Comments   
Comment by Connie Chen [ 26/Mar/20 ]

rachelle.palmer will review to determine priority/what the acceptable impact should be?

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