[SERVER-23635] The 'keyUpdates' metric only reflects the last document updated when performing a multi-update Created: 11/Apr/16 Updated: 06/Dec/22 Resolved: 15/Apr/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Diagnostics, Querying |
| Affects Version/s: | 3.0.11, 3.2.4, 3.3.4 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | James Wahlin | Assignee: | Backlog - Query Team (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Query
|
||||||||
| Operating System: | ALL | ||||||||
| Steps To Reproduce: |
|
||||||||
| Participants: | |||||||||
| Description |
|
The OpDebug::keyUpdates metric is zeroed out on every call to Collection::updateDocument. https://github.com/mongodb/mongo/blob/r3.3.4/src/mongo/db/catalog/collection.cpp#L628-L629 This metric will be removed for 3.4 under |
| Comments |
| Comment by Ian Whalen (Inactive) [ 15/Apr/16 ] |
|
keyupdates will be replaced by keysinserted and keysdeleted via |