[DOCS-3481] Correct the journaling stats explanation for db.serverStatus() Created: 27/May/14 Updated: 01/Jul/14 Resolved: 01/Jul/14 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | v1.3.7 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Alexander Komyagin | Assignee: | Sam Kleinman (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: | |||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 9 years, 33 weeks, 1 day ago | ||||
| Description |
That is not accurate. As per redbeard0531, the reported stats are aggregated for the "dur.timeMs.dt" interval, and not the commit interval. |
| Comments |
| Comment by Sam Kleinman (Inactive) [ 01/Jul/14 ] |
|
The docs now reflect this. |
| Comment by John Morales [ 10/Jun/14 ] |
|
Whoops, Mathias' calendar says he's away on vacation this week, but confirmed my understanding is correct thanks to milkie. samk The revised statement for the docs can be (something like), "...journaling-related operations and performance during the interval measured by dt." |
| Comment by Alexander Komyagin [ 27/May/14 ] |
|
Well, according to the source code, journaledMB is zero'ed at the same time dt is rotated, so I guess so. redbeard0531 should be able to confirm. |
| Comment by John Morales [ 27/May/14 ] |
|
So to clarify for myself, the dur.timeMs.dt (in millis) even applies to the entries outside the dur.timeMs subdocument, such as dur.commitsInWriteLock and dur.journaledMB? |