[SERVER-30073] Put ChunkSizeTracker on the CollectionShardingState Created: 10/Jul/17 Updated: 20/Jul/17 Resolved: 20/Jul/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Dianna Hohensee (Inactive) | Assignee: | Joanna Huang |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding 2017-07-31 |
| Participants: |
| Description |
|
A ChunkSizeTracker object must be instantiated for each collection. A private function should also be added to call the ChunkSizeTracker with the relevant information. Later, the ChunkSplitter call can also be added to this function, when we're ready to activate autosplit on the shards. CollectionShardingState already has onUpdateOp, onInsertOp, etc. functions, into which this new private function can be plugged. |
| Comments |
| Comment by Dianna Hohensee (Inactive) [ 20/Jul/17 ] |
|
Closing. No longer creating a ChunkSizeTracker class; instead, using the ChunkManager's Chunk objects to store size. |
| Comment by Dianna Hohensee (Inactive) [ 10/Jul/17 ] |
|
We have the MetadataManager as a class variable on the CollectionShardingState. You'll probably want to do something similar for ChunkSizeTracker. |