[SERVER-1907] opcounters rollover Created: 07/Oct/10 Updated: 12/Jul/16 Resolved: 11/Nov/10 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.7.3 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Travis Whitton | Assignee: | Eliot Horowitz (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
Looking at db.serverStatus() it appears that opcounter values are overflowing and reporting as negative values after a particular threshold is reached. The query attribute below is an example of this behavior. "opcounters" : { "insert" : 51352645, "query" : -779127550, "update" : 230051534, "delete" : 45755208, "getmore" : 214070596, "command" : 303271802 }, |
| Comments |
| Comment by auto [ 11/Nov/10 ] |
|
Author: {'login': 'erh', 'name': 'Eliot Horowitz', 'email': 'eliot@10gen.com'}Message: handle overflow in opcounters a bit nicer |