Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-36525

If ChunkSplitter doesn't find enough split points, we should set the estimated chunk size to 0

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.1.2
    • Component/s: Sharding
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: