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

Explicitly state nodes in awaitReplication in do_not_advance_commit_point_beyond_last_applied_term.js

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 3.6.15
    • Affects Version/s: 3.6.15
    • Component/s: Replication
    • Labels:
      None
    • Fully Compatible
    • ALL
    • Repl 2019-09-09
    • 50

      In 3.6, awaitReplication calls isMaster on all nodes and then adds them into liveNodes if isMaster is successful. In the case for do_not_advance_commit_point_beyond_last_applied.js, a node can still be in rollback and fail the isMaster call, which means awaitReplication will ignore that node when waiting for the opTimes.

      We should instead pass the list of nodes we explictly want to wait for into awaitReplication so the node will complete rollback before we begin querying on it.

      This is fixed on v4.0 and onwards thanks to this line here.

            Assignee:
            jason.chan@mongodb.com Jason Chan
            Reporter:
            jason.chan@mongodb.com Jason Chan
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: