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

Await configRS optime replication before stopping replication in refine_collection_shard_key_abort_on_stepup.js

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 4.9.0
    • 4.9 Required
    • Sharding
    • None
    • Fully Compatible
    • Sharding 2021-01-25
    • 14

    Description

      In order to perform this refineCollectionShardKey, the shard will try to refresh the collection information from the configsvr using majority read concern and nearest preference. This could fail if the shard tries to refresh from the configsvr secondary that has replication stopped, as it could not satisfy the read concern.

      Currently the refine_collection_shard_key_abort_on_stepup.js test is only awaiting replication before sharding the collection. Later the collection is sharded and then replication stops on the configsvr secondary, with may not have replicated it.

      The proposal is to introduce an awaitReplication() call after the shardCollection.

      Attachments

        Activity

          People

            jordi.serra-torrens@mongodb.com Jordi Serra Torrens
            jordi.serra-torrens@mongodb.com Jordi Serra Torrens
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: