[SERVER-3091] Alter internal metrics to show journaling metadata Created: 13/May/11  Updated: 30/Mar/12  Resolved: 06/Jul/11

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Kenny Gorman Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Participants:

 Description   

It would be great if we could see journaling metrics in serverStatus(). It would be nice to be able to see from a remote client if we are using journaling. Beyond that it would be nice to see the LSN number just so we can track it when we see it in logs or whatever. Also for just testing/sanity it's nice to expose it.

Also, I am curious, when I see BackgroundFlushing information in serverStatus() when in journal mode does this now represent the stats for the O_direct flushes to the log, or does it still refer the fsync() of the data files? If the latter then it would be nice to have a similar section for the journal flush.

The use case I can image is that I could see that my response time to the place where I have the journal is slow and thus I could make the decision to move it to faster media and perhaps speed up my DB. But w/o those metrics, I am left to just try to make it as fast as possible w/o any real measures.



 Comments   
Comment by Kenny Gorman [ 06/Jul/11 ]

Yes, serverStatus.dur is sufficient.

Comment by Eliot Horowitz (Inactive) [ 28/May/11 ]

have you looked at:
db.serverStatus().dur
What's missing from there you think you would like?

Background flushing in server status is unchanged in meaning with --journal
dur shows the new things

Generated at Thu Feb 08 03:02:03 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.