[SERVER-11559] Count ops attempted in write commands in mongos and mongod Created: 04/Nov/13 Updated: 11/Jul/16 Resolved: 11/Feb/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 2.5.3 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Randolph Tan | Assignee: | Siyuan Zhou |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
It is inconsistent about what ops we count. It's not clear whether the count is of ops attempted or ops succeeded. Insert is ops-succeeded, but update is ops-attempted. The counts are inconsistent between mongod and mongos too. The current spec is described in opcounters.js. We should always record any ops attempted, since that's really the measure of load you care about. |
| Comments |
| Comment by Githook User [ 10/Feb/14 ] |
|
Author: {u'username': u'visualzhou', u'name': u'Siyuan Zhou', u'email': u'siyuan.zhou@mongodb.com'}Message: Signed-off-by: Matt Kangas <matt.kangas@mongodb.com> |