[SERVER-66855] Reject setFeatureCompatibilityVersion when split config is installed Created: 28/May/22  Updated: 29/Oct/23  Resolved: 06/Jun/22

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

Type: Improvement Priority: Major - P3
Reporter: Matt Broadstone Assignee: Matt Broadstone
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Backwards Compatibility: Fully Compatible
Sprint: Server Serverless 2022-06-13
Participants:

 Description   

Since FCV does consensus through the oplog, it might be possible for a recipient node to be stuck in an upgrade/downgrade if it is split before it hears that the FCV operation is complete. After discussion with Cloud, we have decided to reject setFeatureCompatibilityVersion commands if there is an active shard split operation since the Cloud code to run FCV changes is resilient to transient failure.



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

Author:

{'name': 'Matt Broadstone', 'email': 'mbroadst@mongodb.com', 'username': 'mbroadst'}

Message: SERVER-66855 Reject setFCV when a split config is installed
Branch: master
https://github.com/mongodb/mongo/commit/d599853df5ccf96ef652a25d18c0d9da7f337d08

Generated at Thu Feb 08 06:06:36 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.