[SERVER-77422] Change DDL lock mode acquisitions Created: 24/May/23 Updated: 29/Oct/23 Resolved: 03/Jul/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Silvia Surroca | Assignee: | Silvia Surroca |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Sprint: | Sharding EMEA 2023-07-10 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
Update the DDL lock mode acquisitions to enable concurrent DDL operations on the same database once the new DDLLockManager infrastructure is ready. Since the new DDLLockManager infrastructure will be guarded under a feature flag, in case of having the feature flag disabled the user should be warned that the lock will be acquired in exclusive mode even if they specified another mode. |
| Comments |
| Comment by Githook User [ 03/Jul/23 ] |
|
Author: {'name': 'Silvia Surroca', 'email': 'silvia.surroca@mongodb.com', 'username': 'silviasuhu'}Message: |