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

Decision to split chunk should happen on shard mongod, not on mongos

    • Type: Icon: Improvement Improvement
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 4.2.0
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Fully Compatible
    • v4.2
    • Sharding 2018-08-13

      As it is, it's possible to get oversized chunks if data is being written to the same chunk from different mongoses, as each mongos would only see a small amount of data going to that chunk and thus won't trigger a chunk split. If the decision on when to split a chunk happened on the shard, then it could know exactly when 64Mb (or whatever the chunk size has been set to) has been written to a chunk, and thus can trigger a split at the right time and prevent chunks from ever going over the chunk size.

            Assignee:
            alyson.cabral@mongodb.com Alyson Cabral (Inactive)
            Reporter:
            spencer@mongodb.com Spencer Brody (Inactive)
            Votes:
            9 Vote for this issue
            Watchers:
            26 Start watching this issue

              Created:
              Updated:
              Resolved: