[SERVER-32992] Report an error when using MongoDB 4.0 binaries with a instance containing V2Unique format index. Created: 30/Jan/18  Updated: 27/Oct/23  Resolved: 02/Aug/18

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Neha Khatri Assignee: Eric Milkie
Resolution: Works as Designed 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
Sprint: Storage Non-NYC 2018-04-09, Storage Non-NYC 2018-07-16, Storage Engines 2018-07-30, Storage Engines 2018-08-13
Participants:

 Description   

Starting MongoDB 4.0 binaries with an instance containing V2Unique format index should be reported as an error. Report a warning message on startup and an error message the first time a V2Unique index is used, to allow users to remove these using a MongoDB 4.0 binary.



 Comments   
Comment by Eric Milkie [ 02/Aug/18 ]

SERVER-32994 is taking care of the documentation changes for this. There was no commit necessary to achieve the goal of this ticket so I'm closing it Works as Designed.

Comment by Neha Khatri [ 01/Aug/18 ]

MongoDB4.0 binary invokes the function ensureAllCollectionsHaveUUIDs on startup. The effect of calling this function at the start-up is that it opens all the databases, instantiating all the collections and indexes in the system. Instantiating a new format unique index validitates the index formatVersion. The formatVersion validation would fail with 4.0 binary and result in a FATAL assertion causing the startup failure.

This is the desired behaviour with 4.0 binary at startup with new format unique index. Since all the indexes are accessed at startup, a warning at the startup looks unnecessary.

Comment by Alexander Gorrod [ 07/May/18 ]

Guess is 3 days work

Comment by Alexander Gorrod [ 13/Feb/18 ]

It makes sense to hold off doing this work until the V2Unique index format is enabled in 4.2

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