The second time call `RemoveShard` failed: move chunk abort.

There're 4 shards in my sharding cluster: shard1, shard2, shard3, shard4. And there's several sharded collection distributed on these shards.

At first, I remove shard2 successfully. Then, I call `removeShard` to remove shard4 but failed with `sh.status()` return always "draining" status.

After I went through the shard4 log I found the error: "Chunk move failed :: caused by :: ShardNotFound: Shard2 not found". So I think the cache-route hasn't been updated since shard2 already removed.

It can be reproduced when I run "_recvChunkStart" command on shard4, I attached the picture on the attachment.