Skip to content

Commit ba5edc3

Browse files
author
Dave Cuthbert
authored
DOCS-14626 restore node (#2382) (#2437)
* DOCS-14626 restore node * DOCS-14626 restore node * Review feedback
1 parent 936ed05 commit ba5edc3

File tree

1 file changed

+20
-8
lines changed

1 file changed

+20
-8
lines changed

source/tutorial/expand-replica-set.txt

Lines changed: 20 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -38,27 +38,39 @@ to manage member processes.
3838
Existing Members
3939
~~~~~~~~~~~~~~~~
4040

41-
You can use these procedures to add new members to an existing
42-
set. You can also use the same procedure to "re-add" a removed
43-
member. If the removed member's data is still relatively recent, it
44-
can recover and catch up easily.
41+
You can use these procedures to add new members to an existing replica
42+
set.
4543

44+
Restore Former Members
45+
~~~~~~~~~~~~~~~~~~~~~~
46+
47+
You can use these procedures to re-add a node that was removed.
48+
49+
If the data on the removed node is relatively recent, the node recovers
50+
and catches up to the rest of the replica set.
51+
52+
.. important::
53+
54+
Avoid creating new replicated collections on the removed node while
55+
it is in standalone mode. If the standalone node rejoins the replica
56+
set, subsequent operations on the new collection produce an error.
4657

4758
Data Files
4859
~~~~~~~~~~
4960

5061
If you have a backup or snapshot of an existing member, you can move
51-
the data files (e.g. the :setting:`~storage.dbPath` directory) to a new system
52-
and use them to quickly initiate a new member. The files must be:
62+
the data files (for example, the :setting:`~storage.dbPath` directory)
63+
to a new system and use them to quickly initiate a new member. The files
64+
must be:
5365

5466
- A valid copy of the data files from a member of the same replica
5567
set. See :doc:`/tutorial/backup-with-filesystem-snapshots`
5668
document for more information.
5769

5870
.. important:: Always use filesystem snapshots to create a copy of a
5971
member of the existing replica set. **Do not** use
60-
:binary:`~bin.mongodump` and :binary:`~bin.mongorestore` to seed a new
61-
replica set member.
72+
:binary:`~bin.mongodump` and :binary:`~bin.mongorestore` to seed a
73+
new replica set member.
6274

6375
- More recent than the oldest operation in the :term:`primary's
6476
<primary>` :term:`oplog`. The new member must be able to become

0 commit comments

Comments
 (0)