DOCSP-3449: Compact Oplog after Reducing Size #3489
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary:
Running
replSetResizeOplog
to reduce the oplog size doesn't automatically reclaim disk space. Users need to runcompact
to retrieve disk space, butcompact
has some edges.Goal is to provide strong guidance on using
compact
after runningreplSetResizeOplog
and clarifying the security requirements forcompact
when running against non-system and systemStaged:
https://docs-mongodbcom-staging.corp.mongodb.com/rkumar/DOCSP-3449/tutorial/change-oplog-size.html
https://docs-mongodbcom-staging.corp.mongodb.com/rkumar/DOCSP-3449/reference/command/replSetResizeOplog.html#behavior
https://docs-mongodbcom-staging.corp.mongodb.com/rkumar/DOCSP-3449/reference/command/compact.html#compact-required-privileges