[SERVER-20733] Mongos should be smart enough to tell if it's connected twice to the same config server Created: 02/Oct/15  Updated: 09/Nov/15  Resolved: 09/Nov/15

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

Type: Bug Priority: Major - P3
Reporter: Dmitry Ryabtsev Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Operating System: ALL
Participants:

 Description   

With three config servers set up it is possible to have a scenario when due to incorrect host names resolution connections to the config servers established incorrectly. For example, mongos, instead of connecting to the config servers #1, #2 and #3 may have two connections to the config server #1, none to #2 and one to #3.

Currently mongos is unable to figure out that something is wrong, despite that any metadata modifications result in a duplicate key exception.

There should be a way for mongos to ensure it is not connected twice to the same config server.



 Comments   
Comment by Andy Schwerin [ 09/Nov/15 ]

Obviated by SERVER-1448, as replica sets perform their own duplicate detection as part of monitoring.

Generated at Thu Feb 08 03:55:06 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.