-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
None
-
Affects Version/s: 3.3.5
-
Component/s: Sharding
-
None
-
Sharding
-
ALL
Unlike the splitChunk command, splitVector does not check if the chunk with the exact boundaries exists before performing a scan on the specified range. This can lead to unnecessary work done by the splitVector since the result will be unusable by the splitChunk command. This is because it will be rejected by the chunk exists check.
- is related to
-
SERVER-22462 Autosplitting failure caused by stale config in runCommand
- Closed