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

Blacklist tests that assert on ismaster field of isMaster response in retryable_writes_jscore_stepdown_passthrough

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.6.7, 3.7.3
    • Component/s: None
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v3.6
    • Sprint:
      Sharding 2018-02-26
    • Linked BF Score:
      0

      Description

      If a stepdown occurs during an isMaster command, the server can return an {ok: 1, ismaster: false} reponse if there is enough time before its connection is cut, since isMaster defaults to slaveOk: true. Tests running in the retryable_writes_jscore_stepdown_passthrough expect to be running against primary nodes only, so this can fail assertions.

      Only two tests in jstests/core assert on this field, ismaster.js and dbadmin.js, and neither provides much value for testing retryable writes across stepdowns, so the simplest way around this is to just blacklist these tests.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              jack.mulrow Jack Mulrow
              Reporter:
              jack.mulrow Jack Mulrow
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: