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

Confirm all nodes have successfully reconfigured before shutdown in auto_safe_reconfig_helper_max_voting_nodes.js

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 7.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • Repl 2023-03-20, Repl 2023-04-03
    • 45
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      There are totally 8 nodes in the config. By looking at the log, it seems that when we do reconfig, node 7(20547) is way behind others in the reconfig process. In the test, we move forward based on whether the reconfig succeeds on majority of nodes, so one slow node doesn't affect the test process, however, when we shutdown the replica set, we do rely on every node to finish the reconfig process or the shutdown will error out, leading to test failure.

      We can add a configuration check for every node to be up-to-date before shutdown replica set, so the test won't fail on replica set shutdown.

            Assignee:
            jiawei.yang@mongodb.com Jiawei Yang
            Reporter:
            jiawei.yang@mongodb.com Jiawei Yang
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: