[SERVER-13186] request for journaling/dur stats that are not reset in db.serverStatus Created: 13/Mar/14 Updated: 06/Dec/22 Resolved: 14/Sep/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | MMAPv1, Storage |
| Affects Version/s: | 2.6.0-rc1 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Mark Callaghan | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | journal, metrics, stats, storage | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Storage Execution
|
| Participants: |
| Description |
|
See https://groups.google.com/forum/#!topic/mongodb-dev/kAu1HTu5sq0. The journaling/dur stats in db.serverStatus() are counters from the last 3 (or maybe from the 3 seconds prior to that). While it is convenient to get recent stats for monitoring this creates problems for external monitoring. My request is for a new set of counters displayed by db.serverStatus() that are journaling/dur stats which don't get reset every 3 seconds |
| Comments |
| Comment by Dwight Merriman [ 15/Mar/14 ] |
|
maybe there is a new section called "journal" and one day "dur" goes away. "dur" was a suboptimal name anyway |
| Comment by Eliot Horowitz (Inactive) [ 15/Mar/14 ] |
|
Easy to duplicate them with a new field to make transition easy. |
| Comment by Dwight Merriman [ 15/Mar/14 ] |
|
the only reason it is that reason is historical – those stats predate a lot of the others and the point-in-time when it was decide to do the cumulative style. it would be better if they were like everything else so the only thing impeding changing it would be backward compatibility. there would need to be some plan and analysis of how much it would mess up existing readers of the stats... |