[SERVER-8949] Is there any major issue with running a 1 shard production setup? Created: 12/Mar/13 Updated: 26/Mar/13 Resolved: 26/Mar/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 2.2.3 |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | Huy Nguyen | Assignee: | Bryan Reinero |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
Hi, We are planning to use sharded replica-set in production and would like to know if there are any issue with just running a single shard? As our data grow, we will add the second. It seems to run fine in our test environment. Your document specifically mentions to run 2 shards: http://docs.mongodb.org/manual/core/sharded-clusters/#infrastructure-requirements-for-sharded-clusters The reason why we're doing this so that we don't have to convert replicaset to a sharded setup later on as the coding requirement is different for findAndRemove/findAndModify (shard key requirement for these calls) and deal with the shard key aspect at a later time. |
| Comments |
| Comment by Bryan Reinero [ 12/Mar/13 ] |
|
Running your cluster as a single sharded system is certainly possible, but there's no effective advantage to doing so. Although you could run a single sharded cluster to get chunk splitting, that's only advantageous if you're preparing to add shards in near future. Chunk splitting marginally increases the number of operations on a system, which although not prohibitive is in this case unnecessary. There can be a slight hit in bulk insertions through mongos, but this can be mitigated by splitting bulk loads across several mongos's. Remember too that sharded clusters include instances of mongos and config servers, which in themselves are not hard to configure nor maintain, but do require proper fail-over and backup considerations. |