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

Remove shard version checks from cursor_valid_after_shard_stepdown

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 5.2.0, 5.1.0-rc0
    • Fix Version/s: 5.2.0, 4.4.11, 5.1.0-rc2, 5.0.5
    • Component/s: Sharding
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v5.1, v5.0, v4.4
    • Sprint:
      Sharding EMEA 2021-11-01
    • Linked BF Score:
      45

      Description

      cursor_valid_after_shard_stepdown.js checks for shard version UNKNOWN after the step up of a secondary. If a refresh happens on the secondary from a mirrored read or other source, this assertion will fail.

      This ticket is to remove the shard versioning checks from this test and re-enable it in the sharding_max_mirroring suite

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              allison.easton Allison Easton
              Reporter:
              allison.easton Allison Easton
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: