Until we do SERVER-50144, removeShard can leave a config.rangeDeletions document in the "pending" state on a moveChunk recipient, and therefore orphans that are not cleaned up on a moveChunk recipient.
In the meantime, we should blacklist tests that call removeShard from the hook that checks that orphans are eventually cleaned up, so that we don't get test failures for this known issue.
- related to
-
SERVER-50144 Removing a shard with in-progress migration coordinators can leave permanently pending config.rangeDeletions document on recipient
- Backlog