[SERVER-31385] ShardingTest.prototype.checkUUIDsConsistentAcrossCluster not resilient to closed connections Created: 04/Oct/17  Updated: 27/Oct/23  Resolved: 03/Mar/22

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

Type: Bug Priority: Major - P3
Reporter: Randolph Tan Assignee: [DO NOT USE] Backlog - Sharding EMEA
Resolution: Gone away Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-31583 Update ShardingTest._connections when... Closed
Related
is related to SERVER-31583 Update ShardingTest._connections when... Closed
is related to SERVER-31668 checkUUIDsConsistentAcrossCluster mus... Closed
Assigned Teams:
Sharding EMEA
Operating System: ALL
Participants:
Linked BF Score: 0

 Description   

The test hook tries to re-use the existing shard connections stored in ShardingTest. However, these connections could have been disconnected (for example, due to stepDown during the test) and will throw an error when used.



 Comments   
Comment by Githook User [ 31/Jan/18 ]

Author:

{'email': 'dianna.hohensee@10gen.com', 'name': 'Dianna Hohensee', 'username': 'DiannaHohensee'}

Message: SERVER-31385 Do not do a UUID consistency check for recovering_slaveok.js

(cherry picked from commit e03a936e50d40cac82685965bdcba9b4d08d553b)
Branch: v3.6
https://github.com/mongodb/mongo/commit/08463308869df203c438d354c6346ad659ed36dd

Comment by Githook User [ 27/Nov/17 ]

Author:

{'name': 'Dianna Hohensee', 'username': 'DiannaHohensee', 'email': 'dianna.hohensee@10gen.com'}

Message: SERVER-31385 Do not do a UUID consistency check for recovering_slaveok.js
Branch: master
https://github.com/mongodb/mongo/commit/e03a936e50d40cac82685965bdcba9b4d08d553b

Comment by Dianna Hohensee (Inactive) [ 22/Nov/17 ]

There are ~70 BFGs on this, so stopping the UUID check in recovering_slaveok.js, until this is resolved correctly.

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

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

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