-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Fully Compatible
-
Sharding EMEA 2022-04-04, Sharding EMEA 2022-04-18
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.
- causes
-
SERVER-81352 Reintroduce check for zoning/draining when serving manual chunk migrations in v6.0+ versions
- Backlog
- depends on
-
SERVER-64486 MoveRange must properly honor secondary throttle settings
- Closed
-
SERVER-64195 Provide user-facing `moveRange` command
- Closed