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

racy test in autodiscover_config_rs_from_secondary.js

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 3.3.12
    • Fix Version/s: 3.4.0-rc4
    • Component/s: Sharding
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Sprint:
      Sharding 2016-10-10, Sharding 2016-10-31, Sharding 2016-11-21
    • Linked BF Score:
      0

      Description

      Test kills all nodes in a config repl set except for one and tries to perform a read on it. However, it is possible that a background thread in mongos advances the latest config server opTime that the surviving secondary has yet to replicate and this will cause the read after opTime to timeout.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: