[SERVER-11339] mongod should not trust first thing mongos tells it Created: 23/Oct/13  Updated: 10/Dec/14  Resolved: 07/Mar/14

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

Type: Bug Priority: Major - P3
Reporter: Asya Kamsky Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-2299 Mongod should know what shard it is a... Closed
Operating System: ALL
Participants:

 Description   

When a shard1 had a failover, the first connection to newly elected primary told it that it was a different shard (shard2). After that it no longer would accept connections from other mongos telling it that it's shard1.

Would be nice if mongod could validate what mongos passes it, which would mean a stray confused mongos will not be able to even connect to mongod successfully if its view of hostnames/etc. is not the same as reality.



 Comments   
Comment by Scott Hernandez (Inactive) [ 29/Oct/13 ]

No, you can specify a shard name when adding a shard; the replica set name is just the default shard name.

Comment by Asya Kamsky [ 29/Oct/13 ]

dan@10gen.com mongod knows the name of its own replica set - isn't that expected to match shard name?

Comment by Daniel Pasette (Inactive) [ 29/Oct/13 ]

I don't believe there's a way for the mongod to validate it's shard name in the way you've described.

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