[DOCS-4511] types and levels of locks description inconsistency Created: 12/Dec/14 Updated: 30/Oct/23 Resolved: 01/Nov/22 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Alex Lerner | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | bite-sized | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 1 year, 14 weeks, 1 day ago | ||||
| Epic Link: | DOCSP-1769 | ||||
| Story Points: | 0.25 | ||||
| Description |
|
There is an inconsistency in the way we describe locks when returned from currentOp(), as an example. According to http://docs.mongodb.org/manual/reference/method/db.currentOp/#currentOp.locks the ^ specifies database level lock, as in:
but according to http://docs.mongodb.org/manual/reference/method/db.currentOp/#currentOp.lockStats the capital "W" means global level lock. This was raised by a customer who was asking about updateAndModify – we know that we do not take a global lock on updateAndModify, so the documentation is wrong |
| Comments |
| Comment by Education Bot [ 01/Nov/22 ] |
|
Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you! |