[SERVER-55494] Retake the collection critical section on step up (in drain mode) Created: 24/Mar/21  Updated: 29/Oct/23  Resolved: 30/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: Sergi Mateo Bellido Assignee: Sergi Mateo Bellido
Resolution: Fixed Votes: 0
Labels: PM-1965-Milestone-1-Rename-Collection, PM-234-Catalog-Work
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-55551 Remove drop index from create collect... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2021-04-05
Participants:

 Description   

The goal of this ticket is to retake the in-memory collection critical section when we are stepping up (but still in drain mode).

The idea is that while we are in drain mode we have to traverse all docs in config.collectionCriticalSections. For each document, we have to take the in-memory critical section in the right phase, clear the filtering metadata and spawn a task that refreshes the collection metadata through onShardVersionMismatch function.



 Comments   
Comment by Githook User [ 30/Mar/21 ]

Author:

{'name': 'Sergi Mateo Bellido', 'email': 'sergi.mateo-bellido@mongodb.com', 'username': 'smateo'}

Message: SERVER-55494 Retake the collection critical section on step up (in drain mode)
Branch: master
https://github.com/mongodb/mongo/commit/b055d3a7093064a4df30a5595e13dc6b6ac0844f

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