[SERVER-23240] MongoDB 3.x wired tiger oplog preallocation sizes inconsistent Created: 18/Mar/16  Updated: 29/Mar/16  Resolved: 29/Mar/16

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

Type: Bug Priority: Major - P3
Reporter: Dharshan Rangegowda Assignee: Unassigned
Resolution: Incomplete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Participants:

 Description   

Hi,

I am using the wired tiger storage engine.

I am finding in consistent results for the oplog preallocation. Sometimes I find the oplog preallocated

local 4.048GB

However in some cases I dont find it preallocated
local 0.089GB

This is for the same sized disk. Is there some optimization done based on the speed of the underlying disk?



 Comments   
Comment by Ramon Fernandez Marina [ 29/Mar/16 ]

dharshanr@scalegrid.net, if this is still an issue for you please post the logs for the affected nodes as requested by Dan above and we'll reopen the ticket to investigate.

Thanks,
Ramón.

Comment by Daniel Pasette (Inactive) [ 19/Mar/16 ]

Can you include the entire log file for each example?

How big is the storage volume where you've set your dbpath? If not specified, mongodb uses /data/db by default.

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