[SERVER-64363] Make cluster moveChunk invoke configsvrMoveRange Created: 09/Mar/22  Updated: 29/Oct/23  Resolved: 06/Apr/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:
Depends
depends on SERVER-64486 MoveRange must properly honor seconda... Closed
depends on SERVER-64195 Provide user-facing `moveRange` command Closed
Problem/Incident
causes SERVER-81352 Reintroduce check for zoning/draining... Backlog
Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2022-04-04, Sharding EMEA 2022-04-18
Participants:

 Description   

Since moveRange is expected to work the same way of moveChunk when both bounds are provided, route moveChunk requests to the move range config command.



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

Author:

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

Message: SERVER-64486 + SERVER-64363 moveRange honors secondary throttle and cluster moveChunk calls into moveRange
Branch: master
https://github.com/mongodb/mongo/commit/fc999fe67861f0c40f432bade6091f70de84f8f1

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