[DOCS-5564] Automation config: ambigious shard definition semantics Created: 04/Jun/15 Updated: 11/Jan/17 Resolved: 27/Jul/16 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Cloud Manager, Ops Manager |
| Affects Version/s: | None |
| Fix Version/s: | 01112017-cleanup |
| Type: | Task | Priority: | Minor - P4 |
| Reporter: | Sam Kleinman (Inactive) | Assignee: | Bob Grabar |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 7 years, 29 weeks ago |
| Epic Link: | docs-replication |
| Description |
|
related to https://docs.mms.mongodb.com/reference/cluster-configuration/#sharding When defining a shard its unclear how to specify shards that aren't replica sets, or if this is even possible. Do you omit the sharding.shards[n].replicaSet field? set it to some magic value? If its not possible to have a shard provided by a stand alone, it might be useful to clearly state that here. |
| Comments |
| Comment by Emily Hall [ 27/Jul/16 ] |
|
Closed for housekeeping on 7/27/2016 by Emily Hall. |