Make replica set primary detection stepdown-proof in concurrency workloads

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.1.12
    • Affects Version/s: None
    • Component/s: Concurrency, Sharding
    • None
    • Fully Compatible
    • ALL
    • Sharding 2019-05-20
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The chunks helper for concurrency workloads has a function to retrieve the primary replica set node from a shard.

      If this function doesn't find a primary node from any of the current nodes, it returns immediately. This is not stepdown-proof, as a node could be transitioning to primary but not yet reporting isMaster: true.

      We should use assert.soon with a short-ish timeout instead of immediately returning and failing a test, similar to what the replica set test class does.

              Assignee:
              Janna Golden
              Reporter:
              Blake Oler
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: