Skip to content

Update master-slave.txt #1927

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

Update master-slave.txt #1927

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
4 changes: 2 additions & 2 deletions source/core/master-slave.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -111,7 +111,7 @@ with a master if:
- The slave stops (i.e. shuts down) and restarts later after the
master has overwritten the relevant operations from the master.

When slaves, are out of sync, replication stops. Administrators must
When slaves are out of sync, replication stops. Administrators must
intervene manually to restart replication. Use the :dbcommand:`resync`
command. Alternatively, the :option:`--autoresync <mongod --autoresync>`
allows a slave to restart replication automatically,
Expand Down Expand Up @@ -250,7 +250,7 @@ Convert a Master-Slave Deployment to a Replica Set

To convert a master-slave deployment to a replica set, restart the
current master as a one-member replica set. Then remove the data
directors from previous secondaries and add them as new secondaries to
directories from previous secondaries and add them as new secondaries to
the new replica set.

1. To confirm that the current instance is master, run:
Expand Down