[SERVER-56788] Extend the in-memory collection critical section to keep track of the ongoing operation Created: 10/May/21  Updated: 29/Oct/23  Resolved: 17/May/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
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-56888 Require a unique identifier in critic... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2021-05-17
Participants:

 Description   

Similarly to what we do in the recoverable critical section, the goal of this ticket is to extend the ShardingMigrationCriticalSection to keep track of which operation is currently using the CS.

As a secondary goal, we should implement its methods in such a way that acquiring the same CS twice it is not an error if the reason is the same.



 Comments   
Comment by Githook User [ 16/May/21 ]

Author:

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

Message: SERVER-56788 Extend the in-memory collection critical section to keep track of the ongoing operation
Branch: master
https://github.com/mongodb/mongo/commit/6d2e673bd7c69aa0de24ba3ce1ac3aa1c71343be

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