[SERVER-64817] Compute missing bound of `moveRange` within MigrationSourceManager Created: 23/Mar/22  Updated: 29/Oct/23  Resolved: 25/Apr/22

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

Type: Bug 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:
Backports
Backwards Compatibility: Fully Compatible
Backport Requested:
v6.0
Sprint: Sharding EMEA 2022-04-18, Sharding EMEA 2022-05-02
Participants:

 Description   

When moveRange is only invoked with one bound, the missing bound is currently computed outside the MigrationSourceManager before running a refresh. Purpose of this ticket is to optimize the current logic by moving the bound calculation after the onShardVersionMismatch to be sure that the routing table is not stale.



 Comments   
Comment by Githook User [ 27/Apr/22 ]

Author:

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

Message: SERVER-64817 Compute missing bound of moveRange within MigrationSourceManager
Branch: v6.0
https://github.com/mongodb/mongo/commit/d3b3466b4958f38d6fb70541c660b520ec9cd678

Comment by Githook User [ 25/Apr/22 ]

Author:

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

Message: SERVER-64817 Compute missing bound of moveRange within MigrationSourceManager
Branch: master
https://github.com/mongodb/mongo/commit/36d3af6e81247713f53065769e73f4f0fa8e622d

Generated at Thu Feb 08 06:01:13 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.