[SERVER-81352] Reintroduce check for zoning/draining when serving manual chunk migrations in v6.0+ versions Created: 22/Sep/23  Updated: 26/Oct/23

Status: Backlog
Project: Core Server
Component/s: None
Affects Version/s: 7.0.1, 6.0.10, 7.1.0-rc3
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Pierlauro Sciarelli Assignee: Backlog - Catalog and Routing
Resolution: Unresolved Votes: 0
Labels: oldshardingemea, shardingemea-qw
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
is caused by SERVER-64363 Make cluster moveChunk invoke configs... Closed
Assigned Teams:
Catalog and Routing
Operating System: ALL
Participants:
Story Points: 2

 Description   

Up until v5.0 , when user was issuing a moveChunk command was being issued by a user, there was a check on the config server side ensuring that the chunk would not:

  • Span across multiple zones
  • Be moved to a draining shard

With the introduction of the moveRange patch in v6.0, that check is not happening anymore.

Purpose of this ticket is to evaluate if it's worth reintroducing such check for user-issued moveChunk/moveRange commands in v6.0+ versions. If yes, it should be reintroduced into this new balancer method.

(Thanks tommaso.tocci@mongodb.com for spotting the change in behavior)


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