-
Type:
Bug
-
Status: Done
-
Priority:
Medium
-
Resolution: Fixed
-
Affects Version/s: 2.0.0, 2.9.0, 2.10.0
-
Fix Version/s: 2.12.0
-
Component/s: Grafana Dashboards
-
Labels:
-
Story Points:2
-
Epic Link:
-
Sprint:Platform Sprint 16, Platform Sprint 26, Platform Sprint 27
-
Needs Review:Yes
-
Needs QA:Yes
I'm gathering metrics via percona/mongodb-exporter and currently trying to understand how replication lag is counting.
When I check `rs.printSlaveReplicationInfo()` on primary - it's not corresponding to the query I've found in MongoDB_Cluster_Summary dashboard https://github.com/percona/grafana-dashboards/blob/master/dashboards/MongoDB_Cluster_Summary.json#L1643
If I change max to min, the value becomes closer to real output of mongo command.
The version of mongodb-exporter is latest (0.8.0)
Thanks in advance.
Steps to reproduce: (cannot reproduce)
Connect to the RS primary and run:
cfg = rs.conf()
cfg.members[1].priority = 0
cfg.members[1].hidden = true
cfg.members[1].slaveDelay = 3600
rs.reconfig(cfg)
Check the exporter. The lag should be 3600 seconds.
Created draft PR with test
- blocks
-
PSMDB-752 optime/optimeDate on the SECONDARY is greater than on PRIMARY
-
- Done
-
- duplicates
-
PMM-6767 MongoDB metrics not captured after upgrading to 2.10.1 version
-
- Done
-
- is duplicated by
-
PMM-6811 MongoDB Cluster Summary: when secondary optime is newer than primary optime, lag incorrectly shows 136 years
-
- Done
-
- relates to
-
PMM-6816 mongoDB exporter v2 release - 0.20.1
-
- Done
-