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

Extend database_and_shard_versioning_all_commands.js to also use movePrimary to make a client or server's databaseVersion stale

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 3.7.4
    • None
    • Sharding
    • None
    • Fully Compatible
    • Sharding 2018-04-09

    Description

      Currently, the database_and_shard_versioning_all_commands.js iterates through every command, and for commands that send databaseVersion, it checks that the shard's cached databaseVersion was refreshed as a result of the command being sent.

      To make the shard's cached databaseVersion stale in between each command, the test drops the database from the shard.

      This ticket is to extend the test to iterate through the commands a second time, but this time use movePrimary instead of dropDatabase. This should clear the shard's cached metadata (as part of the movePrimary critical section), so the next command with a databaseVersion should cause the shard to refresh and find the new databaseVersion.

      Attachments

        Activity

          People

            blake.oler@mongodb.com Blake Oler
            esha.maharishi@mongodb.com Esha Maharishi (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: