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

Blacklist major_version_check.js from sharding_last_stable suite in 3.6

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.6.15
    • Component/s: Sharding
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Sprint:
      Sharding 2019-11-04
    • Linked BF Score:
      37

      Description

      In 3.4, after running split chunk, shards always refresh their metadata, which would cause any command to that shard from the stale mongos to receive a stale config error (which is what happens). In contrast, in 3.6 and up, shards only refresh their metadata if split chunk fails for some reason, which is why major_version_check.js works. We should blacklist this test in the last stable suite.

        Attachments

          Activity

            People

            Assignee:
            matthew.saltz Matthew Saltz
            Reporter:
            matthew.saltz Matthew Saltz
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: