[SERVER-10077] Shard tag limits Created: 02/Jul/13 Updated: 09/Jul/13 Resolved: 09/Jul/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Question | Priority: | Critical - P2 |
| Reporter: | Ranjan Parthasarathy | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
AWS Linux AMI, using 2.4.4 mongo |
||
| Participants: |
| Description |
|
I would like to understand what are the limits around shard tags and also the impact to performance. Is there any limit for the number of tags that can be added? How would it effect the perfomance of balancer if we have 6000+ tags Ranjan |
| Comments |
| Comment by Stennie Steneker (Inactive) [ 09/Jul/13 ] |
|
Hi Ranjan, The SERVER project is for reporting bugs or feature suggestions for the MongoDB server and tools. For MongoDB-related support discussion please post on the mongodb-users group (http://groups.google.com/group/mongodb-user) or Stack Overflow. The normal mechanism for distributing data is choosing a good shard key. Tag-aware sharding makes it possible to associate specific ranges of a shard key with a specific shard or subset of shards, but 6000+ tags sounds like a misuse of the feature. I would encourage you to read on up on the Sharded Cluster documentation to get a better understanding of MongoDB's sharding architecture. For an example of tag-aware sharding, you might find this blog post helpful: Controlling Collection Distribution. Regards, |