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

rollback_with_socket_error_then_steady_state.js should await secondary nodes before db hash checks

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 3.6.0-rc5
    • Affects Version/s: None
    • Component/s: Replication
    • Labels:
      None
    • Replication
    • Fully Compatible
    • ALL
    • 0

      We re-connect all nodes at the end of the test so we can do a db hash check, but we don't wait for any rollbacks to finish, so it is possible we end up calling awaitReplication while a node is in rollback. This leads to us ignoring the node and not waiting for it to catch up. We should await secondary nodes after re-connection and before starting db hash checks.

            Assignee:
            backlog-server-repl [DO NOT USE] Backlog - Replication Team
            Reporter:
            william.schultz@mongodb.com William Schultz
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: