[DOCS-7177] mongos config string order Created: 16/Feb/16  Updated: 11/Jan/17  Resolved: 19/Feb/16

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: mongodb-3.0
Fix Version/s: 01112017-cleanup

Type: Improvement Priority: Major - P3
Reporter: Shakir Sadikali Assignee: Ravind Kumar (Inactive)
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-22485 ShardNotFound error when looking up r... Closed
Participants:
Days since reply: 7 years, 51 weeks, 5 days ago

 Description   

customer reported issues performing clusterwide operations on a portion of the nodes in their cluster. Issue was resolved by setting the --config string to the be the same across all mongos.

The docs imply this needs to be the case only for legacy mirrored instances. It seems it is the case for CSRS as well.



 Comments   
Comment by Randolph Tan [ 19/Feb/16 ]

I was not able to successfully reproduce the bug, but if this is truly SERVER-22485, then the workaround is not to make all mongos have the same --configdb, but to make sure that the host list in the --configdb are sorted in lexicographical order. The new changes in v3.2.3 (specifically, SERVER-21906) should make this issue go away for --configdb strings.

Generated at Thu Feb 08 07:53:44 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.