Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-36689

Free Monitoring metrics values become "stuck" after very long server response

    • Type: Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • ALL
    • Hide

      (I've been struggling to reproduce this locally, so this may have been caused by local dev environment issues, debugger, etc. Still raising the ticket in case you guys are able to reproduce more easily, or are aware of codepaths that might lead to this behavior.)

      Show
      (I've been struggling to reproduce this locally, so this may have been caused by local dev environment issues, debugger, etc. Still raising the ticket in case you guys are able to reproduce more easily, or are aware of codepaths that might lead to this behavior.)

      If the Free Monitoring service takes a very long time (minutes) to respond to a request (because, for instance, execution of service was suspended while stepping through debugger), we later observed that two other mongods had their metrics reporting "stuck" for 4+ hours, in that these two mongods would report metrics every minute, but always repeating the same data points from ~4 hours ago. It never advanced again to steady state reporting of new, current metrics.

            Assignee:
            mark.benvenuto@mongodb.com Mark Benvenuto
            Reporter:
            duncan.armstrong@mongodb.com Duncan Armstrong
            Votes:
            0 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated:
              Resolved: