Details
-
Task
-
Resolution: Done
-
Major - P3
-
None
-
None
Description
Add a section briefly explaining the unavailability windows for collections undergoing a rename in sharded clusters (starting from v5.0).
The following rules apply for both sharded and unsharded collections:
- Source collection is locked on every shard in exclusive way (r/w will get enqueue and eventually timeout)
- Target collection is locked on every shard in exclusive way (r/w will get enqueue and eventually timeout)
- All subsequent operations on the involved collections must wait until renameCollection completes