-
Type: Improvement
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Query Language
-
None
-
Minor Change
-
v5.0
-
Query Optimization 2021-07-12, Query Optimization 2021-07-26, Query Optimization 2021-08-09
-
170
SERVER-57483 partially addressed the regression of $lookup results not being cached by special casing the config.cache.chunks collection. There is still room for significant improvement. It has been found that using ChunkManager to binary search the temporary resharding collection's chunk ranges rather than using DocumentSourceSequentialDocumentCache to scan linearly through the same chunk ranges results in a >10x speedup in the overall collection cloning runtime.
This ticket represents the work to add a custom aggregation stage or expression or otherwise optimize resharding's collection cloning pipeline to achieve the observed >10x speedup.
- is depended on by
-
SERVER-53351 Add resharding fuzzer task with step-ups enabled for shards
- Closed
- is related to
-
SERVER-57483 Results from $lookup stage are not cached for a resharding operation's sub-pipeline
- Closed
- related to
-
SERVER-67529 Resharding silently skips documents with all MaxKey values for their fields under the new shard key pattern
- Closed
-
SERVER-58983 Stub out unit tests enough to re-enable ReshardingCollectionClonerTest suite
- Closed
-
SERVER-57668 Cache chunk bounds as an array in resharding collection cloning pipeline
- Closed