[SERVER-36689] Free Monitoring metrics values become "stuck" after very long server response Created: 15/Aug/18 Updated: 12/Aug/19 Resolved: 06/Sep/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Duncan Armstrong | Assignee: | Mark Benvenuto |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Steps To Reproduce: | (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.) |
| Participants: |
| Description |
|
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. |
| Comments |
| Comment by Mark Benvenuto [ 05/Sep/18 ] |
|
I am closing this ticket due to the lack of repro steps. |
| Comment by Mark Benvenuto [ 21/Aug/18 ] |
|
If there is no repro steps, I cannot proceed to investigate. |
| Comment by Duncan Armstrong [ 15/Aug/18 ] |
|
john.morales originally saw this behavior, so he might be able to provide more detail (I can't seem to tag him from here though?) |