[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: |
|
||||||||
| 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 |