If the primary of a recipient shard goes through unclean shutdown during the "cloning" state and steps up again after restarting, the restored "oplogEntriesFetched" metric can be incorrect since upon recovery it is set to the sum of fast counts on the config.localReshardingOplogBuffer.<collUUID>.<donorShardId> collections and fast counts by design can be incorrect after unclean shutdown. Having an incorrect "oplogEntriesFetched" metric leads to incorrect remaining time estimates and can make resharding enter the critical section too early and hit ReshardingCriticalSectionTimeout error.