When the ChunkSplitter runs, we run splitVector to compute the points where we should split the chunk, and if this returns too few points, we don't split the chunk. In this case, we should set the size in ChunkWritesTracker back to 0 using some new function ChunkSplitStateDriver::abandonPrepare() so that we don't continue to trigger splits where we don't actually need one yet.
- is depended on by
-
SERVER-11794 Split finds 0 split points but split attempts on chunk continue
- Closed