[SERVER-83657] Top::LockType::NotLocked reported when locks are held Created: 28/Nov/23 Updated: 30/Jan/24 |
|
| Status: | Open |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Haley Connelly | Assignee: | Backlog - Query Execution |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Query Execution
|
||||||||
| Participants: | |||||||||
| Description |
|
For example, in _createView, the DB and CollectionLock are acquired for the view's namespace, but Top::LockType::NotLocked is reported. According to the mongodb documentation, even commands should increment the "readLock" and "writeLock" counts. It looks like we rely on the Top::LockType to increment "readLock" and "writeLock". If today's usage of Top::LockType::NotLocked is correct, we should at least add a comment on when to use which LockType in the enum class declaration. |