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

A stepdown might make the test stale_mongos_and_restarted_shards_agree_on_shard_version.js to fail

    XMLWordPrintable

    Details

    • Operating System:
      ALL
    • Backport Requested:
      v4.2, v4.0
    • Steps To Reproduce:
      Hide

      Run the stale_mongos_and_restarted_shards_agree_on_shard_version.js test several times with the sharding_csrs_continuous_config_stepdown test suite.

      Show
      Run the stale_mongos_and_restarted_shards_agree_on_shard_version.js test several times with the sharding_csrs_continuous_config_stepdown test suite.
    • Linked BF Score:
      23

      Description

      The test requires a stale router so any operation performed on a newly restarted shard triggers the behavior described on SERVER-32198. This way any fix of the PM-1645 project can be checked as they're committed. The sharding_csrs_continuous_config_stepdown test suite generates stepdowns, so when the stale router detects a change on the topology, among other operations, invalidates the database cache and refreshes the metadata, bringing it up to date. If this happens before any of the tested operations, it will make the operation to work as designed, and the assertions added to the test to detect the SERVER-32198 behavior will fail. 

        Attachments

          Activity

            People

            Assignee:
            backlog-server-sharding Backlog - Sharding Team
            Reporter:
            marcos.grillo Marcos José Grillo Ramírez
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated: