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)