[DOCS-9052] Comment on: "manual/core/replica-set-oplog.txt" Created: 29/Sep/16  Updated: 30/Oct/23

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Bug Priority: Major - P3
Reporter: Nathan Neulinger Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: collector-298ba4e7, docs-triage
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Location: https://docs.mongodb.com/manual/core/replica-set-oplog/
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.116 Safari/537.36
Referrer: https://www.google.com/
Screen Resolution: 2560 x 1440


Participants:
Days since reply: 1 year, 14 weeks, 2 days ago
Epic Link: DOCSP-1769

 Description   

Maybe this is more of a code feature request, but

x-mongodb:PRIMARY> rs.printReplicationInfo();
configured oplog size: 19760.75839805603MB
log length start to end: 3746secs (1.04hrs)
oplog first event time: Thu Sep 29 2016 14:19:30 GMT+0000 (UTC)
oplog last event time: Thu Sep 29 2016 15:21:56 GMT+0000 (UTC)
now: Thu Sep 29 2016 15:21:57 GMT+0000 (UTC)

Doesn't tell me ANYTHING about how much of the oplog is in use, only what it's current range is. Sure would be nice if this output would include how much of that configured 19G was occupied but that 1.04 hours of entries. (i.e. tell me 'Current used size of oplog: 1234.5678 MB') Obviously at steady state this isn't an issue (and not feasibly to determine), but when validating sizing while first starting up replication it is useful to know without having to go look at file sizes on disk.



 Comments   
Comment by Education Bot [ 31/Oct/22 ]

Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you!

Generated at Thu Feb 08 07:57:29 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.