[SERVER-34439] Implement the top-chunk optimization on the shard Created: 12/Apr/18  Updated: 29/Oct/23  Resolved: 09/Aug/18

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 4.1.2

Type: Task Priority: Major - P3
Reporter: Matthew Saltz (Inactive) Assignee: Matthew Saltz (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Sharding 2018-07-30, Sharding 2018-08-13
Participants:
Case:

 Description   

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.



 Comments   
Comment by Spencer Brody (Inactive) [ 17/Apr/18 ]

FYI alyson.cabral

Generated at Thu Feb 08 04:36:41 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.