Implement the top-chunk optimization on the shard

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.1.2
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Fully Compatible
    • Sharding 2018-07-30, Sharding 2018-08-13
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Currently we perform an 'optimization' called the 'top chunk' optimization where, when a chunk at the end of the shard key range is split, we migrate the split chunk to another shard. When we move the autosplit logic from mongos to mongod, this doesn't work as before, and it breaks tests. We've decided to just remove it since it's not helping that much anyways.

            Assignee:
            Matthew Saltz (Inactive)
            Reporter:
            Matthew Saltz (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: