[SERVER-1859] Issue clear error if can't connect to all machines from a shard Created: 27/Sep/10  Updated: 06/Dec/22  Resolved: 25/Jan/18

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

Type: Improvement Priority: Major - P3
Reporter: Mathias Stearn Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Done Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Sharding
Participants:

 Description   

Each shard must be able to talk to all config servers and at-least one member of each shard's replicaSet. If a user has overzealous firewall rules things will break and the only error will be 10276: "DBClientBase::findOne: transport error".

Perhaps we should have a background job try to connect to everyone once a minute and warn if it can't.



 Comments   
Comment by Gregory McKeon (Inactive) [ 25/Jan/18 ]

Believed to be covered by the ReplicaSetMonitor.

Generated at Thu Feb 08 02:58:15 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.