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

replmonitor_bad_seed.js should await primary node before writing to shard

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 3.5.7
    • Affects Version/s: None
    • Component/s: Replication
    • Labels:
      None
    • Fully Compatible
    • ALL
    • Repl 2017-05-08
    • 0

      replmonitor_bad_seed.js waits for the replica set nodes to be reachable but if a primary is not available (due to step downs for example), the write to the shard may fail:

          // Verify that the replSetMonitor can reach the restarted set
          awaitRSClientHosts(st.s0, replTest.nodes, {ok: true});
      
          assert.writeOK(st.s0.getDB('test').user.insert({x: 1}));
      

      We should call ReplSetTest.awaitNodesAgreeOnPrimary on the replica set before executing the sharded write.

            Assignee:
            spencer@mongodb.com Spencer Brody (Inactive)
            Reporter:
            benety.goh@mongodb.com Benety Goh
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: