Skip to content

Fix replSetStepDown example and use a more realistic number #1398

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

Fix replSetStepDown example and use a more realistic number #1398

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
6 changes: 3 additions & 3 deletions source/tutorial/force-member-to-be-primary.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -98,10 +98,10 @@ This procedure assumes this configuration:

.. code-block:: javascript

db.adminCommand({replSetStepDown:1000000, force:1})
db.adminCommand({replSetStepDown: 86400, force: 1})

This prevents ``m1.example.net`` from being primary for 1,000,000
seconds, even if there is no other member that can become primary.
This prevents ``m1.example.net`` from being primary for 86,400
seconds (24 hours), even if there is no other member that can become primary.
When ``m3.example.net`` catches up with ``m1.example.net`` it will
become primary.

Expand Down