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

Blacklist cursor_valid_after_shard_stepdown from sharding_max_mirroring

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 5.1.0-rc0
    • None
    • Sharding
    • None
    • Fully Compatible
    • ALL
    • 28

    Description

      cursor_valid_after_shard_stepdown assumes that the secondary has no information about the collection on step up. In the max mirroring suite, though, the secondary can have an up to date view of the collection because of mirroring reads, and so theĀ assertion that shardversion should be unknown after step up will not always be true.

      We should prevent this test from running in the max mirroring suite, and provide a comment in the test about the problem, in case this causes issues for other tests and the assertion of unknown version needs to be removed.

      Attachments

        Activity

          People

            allison.easton@mongodb.com Allison Easton
            allison.easton@mongodb.com Allison Easton
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: