[SERVER-24554] checkShardingIndex is too slow when sharding very large collections Created: 14/Jun/16 Updated: 06/Dec/22 Resolved: 12/Nov/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.2.7 |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Randolph Tan | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Won't Do | Votes: | 1 |
| Labels: | max-triage | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Sharding
|
||||
| Sprint: | Sharding 16 (06/24/16) | ||||
| Participants: | |||||
| Description |
|
While attempting to shard a 20TB collection, we discovered that checkShardingIndex can take days to run. We should find out if these checks are necessary, and investigate speeding them up or eliminating them. |