Wait for replication in shardingtest.restartAllConfigServers and shardingtest.restartAllShards

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Cluster Scalability
    • Fully Compatible
    • ALL
    • ClusterScalability Oct13-Oct27
    • 0
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Wait for replication in shardingtest.restartAllConfigServers and shardingtest.restartAllShards to ensure that a node won't enter rollback after. This can cause problems if the action a test takes after the restart caches connections, because they'd be closed, e.g. if we call stopSet immediately after.

            Assignee:
            Janna Golden
            Reporter:
            Janna Golden
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: