SERVER-61416 changed the rename coordinator to be retried indefinitely when hitting any error after entering the blockCrudAndRename phase. The rationale behind the change was the following: since the rename is invoked in parallel on several shards, it would be problematic to fail the operation after it succeeded only on a subset of shards.

Even though that solution avoids introducing catalog inconsistencies on the from/to collections, we could find a more optimized way to safely abort the operation in case rename did not succeed on any shard and the state of from/to collections did not change under the critical section.