[SERVER-12323] findAndModify not counted properly in opcounters Created: 10/Jan/14 Updated: 10/Jan/14 Resolved: 10/Jan/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 2.5.4 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | John Greenall | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Steps To Reproduce: | run db.serverStatus(); run a findAndModify command run db.serverStatus(); note that the # of updates in the opcounter has not changed |
||||||||
| Participants: | |||||||||
| Description |
|
I am doing some performance testing at the moment and find the opcounters very useful. I find it very strange that a findAndModify is not counted as an update. Is this desired behaviour? |
| Comments |
| Comment by Scott Hernandez (Inactive) [ 10/Jan/14 ] |
|
Yes, this is expected. FindAndModify is a command and is counter there. See |