|
The MovePrimaryCoordinator, in case of error during cloning, unblocks the critical section right after dropping the orphaned data on the recipient.
However, releasing the critical section before is also valid and would decrease the read/write blocking period.
Is worth mentioning that dropping the orphaned data on the recipient could take a long time considering the following points:
- The command sent to drop the recipient data attaches a session to join the cloning thread launched by the movePrimary coordinator previously. This was introduced in
SERVER-81229.
- The cloning thread is not aborted in case of a failure on the movePrimary coordinator (like a step-down). Therefore, we will wait for a full cloning before releasing the critical section.
|