[SERVER-63868] Get rid of MoveChunkRequest Created: 22/Feb/22  Updated: 29/Oct/23  Resolved: 04/Jul/22

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

Type: Task Priority: Major - P3
Reporter: Pierlauro Sciarelli Assignee: Enrico Golfieri
Resolution: Fixed Votes: 0
Labels: PM-2323-cleanup
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-63761 Implement first version of moveRange ... Closed
Gantt Dependency
Related
related to SERVER-67768 fix clang-tidy Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2022-06-27, Sharding EMEA 2022-07-11
Participants:

 Description   

Since the IDL-ized ShardsvrMoveRange command is parsing-compatible with the MoveChunkRequest, replace all usages of the latter in order to remove all the duplicated code.

NB: the `writeConcern` is not a member of the ShardsvrMoveRange command, so it will always need to be passed along with the ShardsvrMoveRange. This is the only relevant difference from the MoveChunkRequest that - instead - is doing some dirty magic to get the write concern when deserializing the secondary throttle member.



 Comments   
Comment by Githook User [ 01/Jul/22 ]

Author:

{'name': 'Enrico Golfieri', 'email': 'enrico.golfieri@mongodb.com', 'username': 'enricogolfieri'}

Message: SERVER-63868 replace MoveChunkRequest with ClusterMoveChunkRequest
Branch: master
https://github.com/mongodb/mongo/commit/3867a0ce36b6587c8eee0507c86695278dc5086e

Comment by Enrico Golfieri [ 13/Jun/22 ]

Due to SERVER-65645 we can replace MoveChunkRequest with ClusterMoveChunkRequest generated using IDL

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