[SERVER-54749] Ensure secondaries consistent behavior during rename collection Created: 24/Feb/21  Updated: 29/Oct/23  Resolved: 25/Mar/21

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 5.0.0-rc0

Type: Task Priority: Major - P3
Reporter: Pierlauro Sciarelli Assignee: Sergi Mateo Bellido
Resolution: Fixed Votes: 0
Labels: PM-1965-Milestone-1
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-55148 Extend DDL Utils that acq/rel the col... Closed
Backwards Compatibility: Fully Compatible
Participants:

 Description   

When a shard primary is holding the critical section during rename, secondaries should also be blocked.



 Comments   
Comment by Sergi Mateo Bellido [ 25/Mar/21 ]

Fixed as part of SERVER-55148. These are the relevant changes for this ticket

 

Generated at Thu Feb 08 05:34:22 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.