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

bulk insert can result in too large chunks

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 2.6.0-rc2
    • Fix Version/s: 2.7.0
    • Component/s: Sharding
    • Operating System:
      ALL

      Description

      Mongos performs auto-split checking after batch writes have been applied. However, the auto-split logic currently only limits the maximum split points to 2. So if you have a 1MB chunkSize and jam the batch with 16MB worth of documents, the auto split logic will only split the chunks into 3, instead of 16.

        Attachments

          Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. SERVER-5066 mongos splits should back off when metadata lock is taken and splitting $max or $min

          • Major - P3 - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. SERVER-12581 mapReduce sharded output replace does not fully split

          • Major - P3 - Major loss of function.
          • Closed
          related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-14667 mongos does not move top chunk after auto-split

          • Major - P3 - Major loss of function.
          • Closed

            Activity

              People

              Assignee:
              renctan Randolph Tan
              Reporter:
              renctan Randolph Tan
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: