[SERVER-31426] Fail write to fCV document if admin.system.version collection does not have UUID Created: 05/Oct/17  Updated: 30/Oct/23  Resolved: 20/Oct/17

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 3.6.0-rc1

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

Issue Links:
Related
related to SERVER-31593 master-slave must clone admin.system.... Closed
is related to SERVER-31189 fassert if feature compatibility vers... Closed
Backwards Compatibility: Fully Compatible
Sprint: Repl 2017-11-13
Participants:

 Description   

This will be a safeguard against users arbitrarily upgrading their fCV without running the setFCV command.



 Comments   
Comment by Githook User [ 20/Oct/17 ]

Author:

{'email': 'judah@mongodb.com', 'name': 'Judah Schvimer', 'username': 'judahschvimer'}

Message: SERVER-31189 SERVER-31426 fail rollback on downgrade
Branch: master
https://github.com/mongodb/mongo/commit/b3d26b5f94636870f75b92582d6b7c31190a1295

Comment by Eric Milkie [ 19/Oct/17 ]

I'm not sure this is the right way to go. It looks like this would only work for version 3.6. What are we going to do for this in 3.8 and further?
Also this is problematic for master/slave as you've discovered; I was hoping to avoid any master/slave changes with regard to UUIDs until master/slave is removed.

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