[SERVER-55144] Add a new collection to track which collection critical sections are taken Created: 11/Mar/21 Updated: 29/Oct/23 Resolved: 15/Mar/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| 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: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Sharding 2021-03-22 | ||||||||
| Participants: | |||||||||
| Description |
|
The goal of this new config.collectionCriticalSections shard-local collection is to track which collection critical sections are taken and by which DDL operation. This is needed to be able to resume DDL operations on step-up. We need the following fields:
|
| Comments |
| Comment by Githook User [ 15/Mar/21 ] |
|
Author: {'name': 'Sergi Mateo Bellido', 'email': 'sergi.mateo-bellido@mongodb.com', 'username': 'smateo'}Message: |