Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-85243

Add FCV upgrade/downgrade test for shardCollection creating the updated buckets index on the timeField

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing

      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.

            Assignee:
            Unassigned Unassigned
            Reporter:
            gil.alon@mongodb.com Gil Alon
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: