[SERVER-64148] Atomic `split+move` when moveRange invoked with only one bound Created: 03/Mar/22  Updated: 29/Oct/23  Resolved: 25/Mar/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.0.0-rc0

Type: Task Priority: Major - P3
Reporter: Pierlauro Sciarelli Assignee: Pierlauro Sciarelli
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
causes SERVER-71666 Reduce number of scanned index entrie... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2022-04-04
Participants:

 Description   

Extend `moveRange` to support the split+move scenario: in case only one bound is specified, calculate the correct bounds before instantiating the migration source manager.



 Comments   
Comment by Githook User [ 24/Mar/22 ]

Author:

{'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}

Message: SERVER-64148 Atomic `split+move` when moveRange invoked with only one bound
Branch: master
https://github.com/mongodb/mongo/commit/1632c284ffe1a6d20db88d0ab8324d771347ed58

Generated at Thu Feb 08 05:59:37 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.