[SERVER-85243] Add FCV upgrade/downgrade test for shardCollection creating the updated buckets index on the timeField Created: 16/Jan/24  Updated: 18/Jan/24

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

Type: Task Priority: Major - P3
Reporter: Gil Alon Assignee: Backlog - Catalog and Routing
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-84180 refineCollectionShardKey does not rew... Open
Related
is related to SERVER-77112 shardCollection and createIndex creat... Closed
Assigned Teams:
Catalog and Routing
Participants:

 Description   

SERVER-77112 changed the index created for the shard key {timeField: 1}. SERVER-84180 will update existing indexes from {metaField: 1} to {metaField:1, timeField:1} using the updated index definition, which is {control.min.time: 1. control.max.time:1}. However, we need to ensure that if users use shardCollection and refineCollectionShardKey with this updated definition, they can upgrade/downgrade as usual. This ticket should handle writing that test and adding changes to the FCV upgrade/downgrade process if needed. Some of the scenarios that need to be tested are:

  1. shardCollection with the new index definition, downgrade the FCV, call refineCollectionShardKey, then upgrade FCV again.
  2. shardCollection with downgraded FCV, then upgrade the FCV, confirm that queries work as expected, and then call refineCollectionShardKey.
  3. shardCollection with upgraded FCV, downgrade FCV, and ensure queries work as expected.

Currently, SERVER-77112 is gated by the feature flag AuthoritativeShardCollection belonging to PM-1941. This change should be made before the feature flag is enabled.


Generated at Thu Feb 08 06:57:14 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.