-
Type: Improvement
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Storage
-
Minor Change
-
Storage Engines 2018-07-30, Storage Engines 2018-08-13
-
0
New format unique indexes would be initially gated by a variable. Start using FCV to enable or disable new format unique indexes:
- Plug-in new format indexes into upgrade/downgrade infratructure.
- Setting FCV=4.2 will cause all exisinting unique indexes to be updated to new format. The content of indexes will not change. New entries will be in new format.
- With FCV=4.0, existing new format index will remain in this format. Any new unique indexes will be created in old V2 format.
- Enhance multiVersion test for collectionsPendingDrop.
- depends on
-
SERVER-34745 Enhance SDI::cursor API seekExact's unittest for new format unique indexes
- Closed
-
SERVER-34838 Fix multiVersion test failure seen with new unique indexes on binary downgrade
- 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-35420 Remove stable optime candidates list from ReplicationCoordinator
- Closed
-
SERVER-35344 Stable timestamp and _currentCommittedSnapshot are redundant
- Backlog
-
SERVER-32991 When V2Unique format indexes are present show a warning message when FCV=4.0 is set
- Closed
-
SERVER-33535 Add microbenchmark tests for mixed entries (old and new) in new unique index
- Closed
- is duplicated by
-
SERVER-32990 Make sure that V2Unique indexes operate correctly after downgrade using MongoDB 4.2 binaries
- Closed
- related to
-
SERVER-36458 Investigate microbenchmark regression with timestamp safe unique indexes
- Closed