-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Cluster Scalability
-
None
-
None
-
None
-
None
-
None
-
None
-
None
When we failed to acquire the critical section in the migration destination, we call release critical section and deleteMigrationRecipientRecoveryDocument (especially this one, as it waits for durable config time) before transitioning state to fail.
The extra delay can also make the _recvChunkCommit command wait unnecessarily. This is not ideal as the migration source holds the critical section while calling _recvChunkCommit.