Skip to content

Commit 40c3698

Browse files
author
Dave Cuthbert
authored
DOCS-14626 restore node (#2382) (#2435)
* DOCS-14626 restore node * DOCS-14626 restore node * Review feedback
1 parent facdcee commit 40c3698

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
@@ -37,27 +37,39 @@ to manage member processes.
3737
Existing Members
3838
~~~~~~~~~~~~~~~~
3939

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

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

4657
Data Files
4758
~~~~~~~~~~
4859

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

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

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

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

0 commit comments

Comments
 (0)