-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
None
-
Affects Version/s: 2.4.9, 2.6.0-rc1
-
Component/s: Diagnostics, Replication
-
None
-
ALL
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).
- is duplicated by
-
TOOLS-586 Standardised column contents for mongostat in chained replication
- Closed