[SERVER-36525] If ChunkSplitter doesn't find enough split points, we should set the estimated chunk size to 0 Created: 08/Aug/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

Issue Links:
Depends
is depended on by SERVER-11794 Split finds 0 split points but split ... Closed
Backwards Compatibility: Fully Compatible
Participants:

 Description   

When the ChunkSplitter runs, we run splitVector to compute the points where we should split the chunk, and if this returns too few points, we don't split the chunk. In this case, we should set the size in ChunkWritesTracker back to 0 using some new function ChunkSplitStateDriver::abandonPrepare() so that we don't continue to trigger splits where we don't actually need one yet.



 Comments   
Comment by Githook User [ 09/Aug/18 ]

Author:

{'name': 'Matthew Saltz', 'email': 'matthew.saltz@mongodb.com', 'username': 'saltzm'}

Message: SERVER-36525 Set the estimated chunk size to 0 when a chunk split is triggered too early
Branch: master
https://github.com/mongodb/mongo/commit/85151e8c7428c6e4f45512e55afe0aa180c795b1

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