[SERVER-34316] Directly take DBLock and CollectionLock in onCannotImplicitlyCreateCollection Created: 04/Apr/18 Updated: 29/Oct/23 Resolved: 05/Apr/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.7.3 |
| Fix Version/s: | 3.7.4 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Esha Maharishi (Inactive) | Assignee: | Esha Maharishi (Inactive) |
| 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-04-09 |
| Participants: |
| Description |
|
We should not use the RAII helpers when taking the collection lock in onCannotImplicitlyCreateCollection (to check if the collection has already been created), because they can throw in the shardVersion or databaseVersion checks. |
| Comments |
| Comment by Githook User [ 05/Apr/18 ] |
|
Author: {'email': 'esha.maharishi@mongodb.com', 'name': 'Esha Maharishi', 'username': 'EshaMaharishi'}Message: |