[DOCS-14642] Add resource locking section for sharded clusters in rename collection documentation Created: 13/Jul/21  Updated: 13/Nov/23  Resolved: 25/Aug/21

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 5.0 Required, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Task Priority: Major - P3
Reporter: Pierlauro Sciarelli Assignee: Jason Price
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 2 years, 24 weeks, 2 days ago
Epic Link: DOCSP-15042
Story Points: 3

 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


 Comments   
Comment by Githook User [ 23/Aug/21 ]

Author:

{'name': 'jason-price-mongodb', 'email': 'jshfjghsdfgjsdjh@aolsdjfhkjsdhfkjsdf.com'}

Message: DOCS-14642 add resource locking section
Branch: master
https://github.com/mongodb/docs/commit/09b64e3c6cb99cbbb89e7a80d92bb04ff59a18f3

Generated at Thu Feb 08 08:10:51 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.