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

"chunk too big to move" and "chunk not full enough to trigger auto-split"

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 3.2.5, 3.2.6
    • Component/s: Sharding
    • None
    • ALL

      When I tried to convert a huge collection (about 0.4 billion records) to a sharding collection, I found it could not move the chunks and could not split the chunks.

      When the balance tried to move the chunk, I got the following error:

      2016-05-24T15:22:52.418+0800 I SHARDING [Balancer] moveChunk result: { chunkTooBig: true, estimatedChunkSize: 33553905, ok: 0.0, errmsg: "chunk too big to move" }
      2016-05-24T15:45:26.569+0800 W SHARDING [conn132080234] cannot move chunk: the maximum number of documents for a chunk is 250001 , the maximum chunk size is 67108864 , average document size is 133. Found 252289 documents in chunk
      

      When it tried to split the chunk, I got the following error:

      2016-05-24T15:22:52.530+0800 I SHARDING [Balancer] split results: CannotSplit: chunk not full enough to trigger auto-split
      

      I use default chunk size 64MB.

      mongos> db.settings.find()
      { "_id" : "chunksize", "value" : NumberLong(64) }
      

      It seems that it fails to move because the record count is > 250001, and fails to split because the chunk size is not large enough?

      My mongodbs version are 3.2.5 and 3.2.6.

            Assignee:
            Unassigned Unassigned
            Reporter:
            bydsky xihui he
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: