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

racy test in autodiscover_config_rs_from_secondary.js

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • 3.4.0-rc4
    • 3.3.12
    • Sharding
    • None
    • Fully Compatible
    • ALL
    • Sharding 2016-10-10, Sharding 2016-10-31, Sharding 2016-11-21
    • 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

        Activity

          People

            randolph@mongodb.com Randolph Tan
            randolph@mongodb.com Randolph Tan
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: