Skip to content

DOCS-7158: suspend automation before resizing oplog #2724

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

DOCS-7158: suspend automation before resizing oplog #2724

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions source/tutorial/change-oplog-size.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -50,6 +50,18 @@ Procedure
- Restart the :program:`mongod` instance as a member of the replica
set.

.. admonition:: Cloud Manager and Ops Manager

If your MongoDB deployment is managed by Cloud Manager or Ops
Manager, suspend automation for each replica set member
whose oplog you wish to resize.

See: *Suspend or Resume Automation for a Process* in the
:mms-docs:`Cloud Manager </tutorial/suspend-automation>` or
:opsmgr:`Ops Manager </tutorial/suspend-automation>` documentation
for instructions. Once you have completed resizing the oplog, you
can resume automation.

Restart a Secondary in Standalone Mode on a Different Port
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Expand Down