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

Chunk counld not split when the chunksize greater than specified chunksize

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Done
    • Affects Version/s: 3.0.1
    • Fix Version/s: None
    • Component/s: Sharding
    • Labels:
    • Operating System:
      Linux

      Description

      Here is the situation:
      There is a chunk, has the shard key range [10001, 100030), but currently, it has only one key (e.g. 10001) has the data, key range from [10002, 10030) is just empty, the chuck data is beyond 8M, then we set the current chuck size to 8M.
      After we fill the data in the key range(10002, 10030), this chunk starts to split, and stopped at a key range like this [10001, 10003), it has two keys, and we just wonder if this is OK or not. From the document on the official site we thought that the chunk might NOT contains more than ONE key.
      So, would you please help us make sure if this is ok or not ?
      What we want to is to split the chunks as many as possible, so that to make sure the data is balanced.

        Attachments

          Activity

            People

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

              Dates

              • Created:
                Updated:
                Resolved: