[SERVER-16325] HTTP console UI asserts if clock jumps backwards Created: 25/Nov/14 Updated: 15/Jan/15 Resolved: 15/Jan/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | HTTP Console |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Tom Blamer | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Operating System: | ALL |
| Steps To Reproduce: |
|
| Participants: |
| Description |
|
The HTTP console UI hits an assert in db/stats/snapshots.cpp if the system clock has been set back in time recently. Including when the clock has been set automatically by ntpd. This results in the below messages, and an HTTP 500 error from the HTTP console: mongodb 2.0.4
mongodb 2.4.9
This is probably the same underlying issue as My plan to avoid hitting this again is to enable the REST API with --rest, and have our monitoring tool use that instead. My thought is that since this only seems to affect the DbTopStatus and WriteLockStatus objects, can the failure be caught in there, and not prevent the entire HTTP console from loading? |
| Comments |
| Comment by Ramon Fernandez Marina [ 15/Jan/15 ] |
|
While showing the current error message may not be very user-friendly, I think it's hard to say what should the HTTP console do and display if the clock jumps back significantly. What I would recommend is the use of the shell to gather whatever metrics are needed, as this method is not affected if the clock jumps backwards. Given that, as of right now, the HTTP console is not a top priority, I'm going to resolve this issue. This decision can be revisited at a later time depending on interest, priorities, and resource availability. Regards, |