Uploaded image for project: 'Percona Monitoring and Management'
  1. Percona Monitoring and Management
  2. PMM-4547

MongoDB dashboard replication lag count incorrect

    XMLWordPrintable

    Details

    • Story Points:
      2
    • Epic Link:
    • Sprint:
      Platform Sprint 16, Platform Sprint 26, Platform Sprint 27
    • Needs Review:
      Yes
    • Needs QA:
      Yes

      Description

      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

       

        Attachments

          Issue Links

          blocks

          Bug - A problem which impairs or prevents the functions of the product. PSMDB-752 optime/optimeDate on the SECONDARY is greater than on PRIMARY

          • Medium - Minor loss of function, or other problem where easy workaround is present.
          • Done
          duplicates

          Bug - A problem which impairs or prevents the functions of the product. PMM-6767 MongoDB metrics not captured after upgrading to 2.10.1 version

          • High - Crashes, loss of data, severe memory leak.
          • Done
          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. PMM-6811 MongoDB Cluster Summary: when secondary optime is newer than primary optime, lag incorrectly shows 136 years

          • High - Crashes, loss of data, severe memory leak.
          • Done
          relates to

          Improvement - An improvement or enhancement to an existing feature or task. PMM-6816 mongoDB exporter v2 release - 0.20.1

          • Medium - Minor loss of function, or other problem where easy workaround is present.
          • Done

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              vvol Vlad Voloshyn
              Votes:
              0 Vote for this issue
              Watchers:
              13 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - Not Specified
                  Not Specified
                  Logged:
                  Time Spent - 1 day, 5 hours, 45 minutes
                  1d 5h 45m

                    Smart Checklist