[SERVER-5960] mongos config server order should not matter Created: 29/May/12  Updated: 15/Feb/13  Resolved: 18/Sep/12

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

Type: Bug Priority: Minor - P4
Reporter: Site Operations Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-1448 Host sharding config data on a replic... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:

 Description   

Per http://groups.google.com/group/mongodb-user/browse_thread/thread/410b9004606d3648 the order of config servers across all mongos processes needs to be the same for sharding to work properly. Is there any reason that has to be true, versus normalizing the hosts internally so the command line can specify servers in any order?



 Comments   
Comment by Scott Hernandez (Inactive) [ 29/May/12 ]

This is by design for a few reason and will be addresses with this issue most likely: SERVER-1448

The order is very important at the moment.

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