[SERVER-30211] Create function inside CollectionShardingState to determine whether a chunk should be auto-split. Created: 18/Jul/17 Updated: 30/Oct/23 Resolved: 28/Aug/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.5.10 |
| Fix Version/s: | 3.5.11 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Hugh Han | Assignee: | Hugh Han |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | sharding | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding 2017-07-31 |
| Participants: |
| Description |
|
Currently, inside cluster_write.cpp's updateChunkWriteStatsAndSplitIfNeeded function, we check whether a chunk should be auto-split, depending on its current size and its desired chunk size. Because we want to move the auto-split logic to the mongod side, this logic should be able to be called from OpObserver::onUpdate and OpObserver::onInserts. To make this possible, this logic will be encapsulated into a private function within CollectionShardingState, to be later called by CollectionShardingState::onUpdateOp and CollectionShardingState::onInsertOp, once the splitVector and splitChunk code has been refactored onto the mongod side. |
| Comments |
| Comment by Githook User [ 26/Jul/17 ] |
|
Author: {'email': 'hughhan1@gmail.com', 'username': 'hughhan1', 'name': 'Hugh Han'}Message: Currently, inside cluster_write.cpp's updateChunkWriteStatsAndSplitIfNeeded function, we check whether a chunk should be auto-split, depending on its current size and its desired chunk size. In this commit, we make this logic possible from within CollectionShardingState's onUpdateOp and onInsertOp functions. |