[SERVER-13248] Do not include "local.slaves" writes in opcounters Created: 18/Mar/14 Updated: 30/Jan/15 Resolved: 27/Aug/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Diagnostics, Replication |
| Affects Version/s: | 2.4.9, 2.6.0-rc1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Asya Kamsky | Assignee: | Matt Dannenberg |
| 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 appears that update counter is incremented when secondary updates local.slaves collection. When there is chaining this gives counts of updates on secondary which looks wrong since a host that's never been primary should only have repl opcounts for writes. There is a precedent for this since we already exclude various other system-initiated writes from opcounters (TTL, from migrate, etc). |
| Comments |
| Comment by Scott Hernandez (Inactive) [ 30/Jan/15 ] |
|
It should be noted that any writes to the local database will be reflected in these counters, since one can write to the local db of replicas who are not primary, so one should expect to see non-zero insert/update/deletes in the opcounters. |
| Comment by Eric Milkie [ 27/Aug/14 ] |
|
2.7 has removed writes to local.slaves completely, so this is no longer a problem. |