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

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

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.2.0
    • Component/s: Sharding
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Backport Requested:
      v4.2
    • Sprint:
      Sharding 2018-08-13
    • Case:

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                Created:
                Updated:
                Resolved: