[SERVER-69558] oplog resize Created: 09/Sep/22  Updated: 09/Sep/22  Resolved: 09/Sep/22

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

Type: Bug Priority: Major - P3
Reporter: Ranjith Kumar Assignee: Yuan Fang
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
Operating System: ALL
Participants:

 Description   
Hi,
We use percona backup for mongodb to take logical backups and the backup got failed with below error:
oplog: unable to upload chunk {1662454473 1}.{1662623412 5}: read data: oplog has insufficient range, some records since the last saved ts {1662454473 1} are missing
Solution provided is to resize the oplog.
So,We want to change the oplog size from 50 GB to 100GB on database ( primary/secondary/Hidden nodes).
Where these oplog storage should reside, on the filesystem storage or the system memory?
Also what should be the impact on overall database performance if we increase the oplog.
please clarify.
MongoDB server version: 4.4.13
Thanks,

Ranjith.



 Comments   
Comment by Yuan Fang [ 09/Sep/22 ]

Close this ticket as it is duplicated by SERVER-69557

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