Details
Description
Addition of new index format allows use of both V2 and V2Unique format. Initially we would add a gating variable to select the unique index format. Switch to FCV as the deciding factor for which format should be used.
- Setting FCV=4.2 will cause all unique indexes to be updated to V2Unique. Do not update the content of the indexes.
- Having FCV=4.0 would create older V2 format indexes
Attachments
Issue Links
- depends on
-
SERVER-32757 Resolve any fallout due IndexVersion bump in mongodb
-
- Closed
-
-
SERVER-33458 With index version bump, update jstests to check for the new index version
-
- Closed
-
-
SERVER-33459 Investigate test failures in sharding_last_stable_mongos_and_mixed_shards with (unique) index bump
-
- Closed
-
- is depended on by
-
SERVER-34954 Verify unique index version upgrade for new --shardsvr nodes added to FCV 4.2 replica set shards
-
- Closed
-
-
SERVER-32992 Report an error when using MongoDB 4.0 binaries with a instance containing V2Unique format index.
-
- Closed
-
-
SERVER-32996 Enhance multiversion test framework to test V2Unique indexes
-
- Closed
-
- is duplicated by
-
SERVER-32996 Enhance multiversion test framework to test V2Unique indexes
-
- Closed
-
- related to
-
SERVER-32995 Execute tests to ensure correct index operation after FCV and version transitions.
-
- Closed
-
-
SERVER-34263 Make new format unique index creation dependent on WT specific data format version
-
- Closed
-