SERVER-85145Backlog
ShardNotFound error should not be bubbled up when concurrently removing a shard and running operations
In HELP-54194, we discovered that there are some commands that may fail when a removeShard is taking place / draining a shard. As an example “listIndexes”. It is expected to hit ShardNotFound as a transient error triggered by a specific timing and in a specific window of time, and bubble up to the user application. The command failed can be perfectly retried and successfully executed after that. The exact reproducible test is attached to the comments. The problem is that the user will be able