Update ShardingTest._connections when a replica set is restarted

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Gone away
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • Sharding EMEA 2021-12-27, Sharding EMEA 2022-01-10
    • 0
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      ShardingTest has some restart functions – restartMongos, restartMongod, etc. – that additionally update ShardingTest._connections, but it doesn't have any restartReplicaSet functionality that would update ShardingTest._connections.

      We need a new ShardingTest function that wraps around ReplSetTest.stopSet() and ReplSetTest.startSet() and updates ShardingTest._connections.

      ------------- motivation below ------------

      checkUUIDsConsistentAcrossCluster uses ShardingTest._connections to get shard primary targeting information. It directly calls listCollection against what it thinks in the shard primary, here, but because key_rotation.js restarts a shard replica set directly, here, ShardingTest._connections probably isn't getting updated with the latest information.

            Assignee:
            Marcos José Grillo Ramirez
            Reporter:
            Dianna Hohensee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: