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

Update ShardingTest._connections when a replica set is restarted

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Major - P3
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: Backlog
    • Component/s: Sharding
    • Labels:
      None
    • Linked BF Score:
      0

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated: