[SERVER-34638] Get rid of CollectionLock::relockAsDatabaseExclusive Created: 24/Apr/18 Updated: 29/Oct/23 Resolved: 24/Apr/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code |
| Affects Version/s: | None |
| Fix Version/s: | 3.7.7 |
| Type: | Improvement | Priority: | Trivial - P5 |
| Reporter: | Kaloian Manassiev | Assignee: | Kaloian Manassiev |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding 2018-05-07 |
| Participants: |
| Description |
|
After the cleanup of the AutoGetter classes, there are no more usages of CollectionLock::relockAsDatabaseExclusive. In order to prevent any future usages of it getting introduced, it should be removed from the codebase. |
| Comments |
| Comment by Githook User [ 24/Apr/18 ] |
|
Author: {'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm', 'name': 'Kaloian Manassiev'}Message: |