[SERVER-31583] Update ShardingTest._connections when a replica set is restarted Created: 16/Oct/17  Updated: 27/Oct/23  Resolved: 10/Jan/22

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: Marcos José Grillo Ramirez
Resolution: Gone away Votes: 0
Labels: sharding-wfbf-sprint
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-31385 ShardingTest.prototype.checkUUIDsCons... Closed
Related
related to SERVER-31385 ShardingTest.prototype.checkUUIDsCons... Closed
related to SERVER-31529 Add TestData.skipCheckingUUIDsConsist... Closed
is related to SERVER-31668 checkUUIDsConsistentAcrossCluster mus... Closed
Sprint: Sharding EMEA 2021-12-27, Sharding EMEA 2022-01-10
Participants:
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.



 Comments   
Comment by Marcos José Grillo Ramirez [ 10/Jan/22 ]

The requested functionality was already implemented by SERVER-33444, is called restartShardRS so closing this ticket so it's dependencies can be unblocked.

Comment by Max Hirschhorn [ 19/Nov/21 ]

We assigned this back to Sharding EMEA because it looks like SERVER-31385 which is assigned to them needs it the most. Either team can in general do work on ShardingTest but any urgency on this task seems like it'd come up first for Sharding EMEA.

Comment by Dianna Hohensee (Inactive) [ 16/Oct/17 ]

SERVER-31385 is basically the same problem, so these two tickets should be addressed together with one solution.

Generated at Thu Feb 08 04:27:32 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.