By design, the MultiUpdateCoordinator and its corresponding MigrationBlockingOperationCoordinator must be running on the same shard. If a movePrimary happens concurrently, it's possible that these run in different places, which can cause problems (see BF-39044).

The MultiUpdateCoordinator should fail and have mongos retry if a concurrent movePrimary commits before it can start a migration blocking operation.