[SERVER-35134] Remove addUUID functions for 4.2 Created: 21/May/18  Updated: 29/Oct/23  Resolved: 18/Jun/18

Status: Closed
Project: Core Server
Component/s: Storage, Upgrade/Downgrade
Affects Version/s: None
Fix Version/s: 4.1.1

Type: Task Priority: Major - P3
Reporter: Maria van Keulen Assignee: Ben Judd
Resolution: Fixed Votes: 0
Labels: neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Storage NYC 2018-06-18, Storage NYC 2018-07-02
Participants:

 Description   

As of MongoDB 4.0, we fail to start up unless all collections have UUIDs to account for 3.4 to 3.6 UUID assignment bugs. To reduce the number of situations in which users have to set the FCV back to 3.4 and to 3.6 again to re-assign UUIDs, non-replicated collections automatically get assigned UUIDs on start up. All such UUID fix-up code should be removed in 4.2, as it is risky to keep around. Skip-level upgrades from 3.6 to 4.2 are prohibited, so it should be safe to isolate UUID fix-up code to MongoDB 4.0.



 Comments   
Comment by Githook User [ 18/Jun/18 ]

Author:

{'username': 'Icantjuddle', 'name': 'Ben Judd', 'email': 'ben.judd@10gen.com'}

Message: SERVER-35134 Remove UUID fixup code, instead fail fast for collections
without UUIDS. By 4.0 all collections should have them.
Branch: master
https://github.com/mongodb/mongo/commit/62b7707c8dc29f786f26fd1762066efe4b64cd37

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