[SERVER-74030] Consider a better way to express recursive locking of DBLock in CollectionSnapshots API Created: 15/Feb/23 Updated: 21/Jul/23 Resolved: 21/Jul/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Jordi Serra Torrens | Assignee: | [DO NOT USE] Backlog - Sharding EMEA |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Assigned Teams: |
Sharding EMEA
|
||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
A way that does not involve using a shared_ptr. |
| Comments |
| Comment by Jordi Serra Torrens [ 21/Jul/23 ] |
|
Closing as shared_ptr seems like a good way to express the ownership relationship, and |