Await replication on config server after shardCollection in safe secondary reads tests

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 3.6.6, 4.0.1, 4.1.1
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Fully Compatible
    • ALL
    • v4.0, v3.6
    • Sharding 2018-07-16
    • 35
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      We should await replication on the config server after shardCollection is called because we read from the nearest config when refreshing, and can potentially read stale metadata.

            Assignee:
            Matthew Saltz (Inactive)
            Reporter:
            Janna Golden
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: