[SERVER-78993] Operations Manager oplog backup creating lot of small oplog slices instead of 10MB Created: 14/Jul/23 Updated: 27/Oct/23 Resolved: 08/Aug/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | waseem khan | Assignee: | Chris Kelly |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Operating System: | ALL |
| Steps To Reproduce: | Operations Manager 6.0 MongDB database version: 4.4.15 enterprise 1>Setup operations manager S3 storage to backup mongodb oplogs and snapshots. 2>Monitor oplog slice generation and not down size when no load is running
|
| Participants: |
| Description |
|
Replica Set (3 Members) backup from operations manager to s3 oplog store is creating lot of oplog slices of very small size instead of 10MB as claimed in documentation(snapshot attached)
Current Behaviour: For three member replica set 60 oplog slices are getting even when no data is being written. Expected Behaviour: Oplog slice should be atleast 10MB
Ask: Is thier any parameter to set oplog block size to higher value so less number of oplogs slices are generated.
Queries: 1>Does op log size increase with number of replica sets with no change in data? 2>Is their any other way oplog slice numbers being written to S3 can be reduced |
| Comments |
| Comment by Evin Roesle [ 08/Aug/23 ] |
|
This works as designed. Ops Manager sends oplog slices every minute or 10MB, whichever comes first. This is not editable. For more information please see our Ops Manager documentation, https://www.mongodb.com/docs/ops-manager/current/tutorial/nav/backup-storage/ . |