[SERVER-3230] Can capped collection auto increase size and sharding Created: 09/Jun/11 Updated: 29/Aug/11 Resolved: 10/Jun/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | eleven huang | Assignee: | Scott Hernandez (Inactive) |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | auto_increase, capped_collection, sharding | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Participants: | |||||||||||||
| Description |
|
Does capped collection can auto increase size and sharding? Thanks! |
| Comments |
| Comment by eleven huang [ 12/Jun/11 ] |
|
Thanks for your answer. |
| Comment by Scott Hernandez (Inactive) [ 10/Jun/11 ] |
|
I have linked to the existing issues for both things you have asked for. If you need more write throughput you can either add more disks (to the single server) or add more machines (w/sharding, for example). You cannot shard a capped collection yet. But you can create multiple capped collections on different shards to increase write throughput; however, you must then run multiple queries to access all your data. |