[SERVER-65322] Get rid of legacy `moveChunk` path once NOMAS milestone 1 is completed Created: 07/Apr/22  Updated: 29/Oct/23  Resolved: 22/Mar/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.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-61557 Get rid of top chunk migration Closed
Assigned Teams:
Sharding EMEA
Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2023-02-20, Sharding EMEA 2023-03-06, Sharding EMEA 2023-03-20, Sharding EMEA 2023-04-03
Participants:

 Description   

Following the introduction of `moveRange` in v6.0, that review the move chunk paths to get rid of all the unused code.

Examples:

  • Get rid of the moveChunk alias since only moveRange must be called by the CSRS in case of FCV >= v6.0 (keep in mind multiversion compatibility)
  • Get rid of _configsvrMoveChunk command as routers are calling into moveRange even if users invoke moveChunk (keep in mind multiversion compatibility)
  • Get rid of all requestMoveChunk calls in favour requestMoveRange and remove of all the dead code around (e.g. MoveChunkCommandInfo that will not be useful anymore)


 Comments   
Comment by Githook User [ 21/Mar/23 ]

Author:

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

Message: SERVER-65322 Get rid of legacy `moveChunk` path once NOMAS milestone 1 is completed
Branch: master
https://github.com/mongodb/mongo/commit/f5c96824b007d8a9208b90b21919d6995651f72d

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