[SERVER-48996] Race between isMaster response connection hook and RSM topology change triggers ShardNotFound Created: 19/Jun/20  Updated: 09/Jul/20  Resolved: 09/Jul/20

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 4.4.0-rc0, 4.3.5, 4.3.6, 4.4.0-rc10
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Tommaso Tocci Assignee: Lamont Nelson
Resolution: Duplicate Votes: 0
Labels: non-blocking
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
is related to SERVER-48201 ShardRegistry::reload() competes with... Closed
Operating System: ALL
Participants:
Linked BF Score: 35

 Description   

On the reception of a isMaster response the RSM installs the new server description and possibly changes the topology type for the corespondent replica set. The same isMaster response will also trigger a NetworkConnectionHook::vlidateHost() that will try to do a reverse lookup host->shard that will fail triggering a ShardNotFound error.


Generated at Thu Feb 08 05:18:39 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.