From 85b11a65207c02b3fbff673846a4befce858d9f7 Mon Sep 17 00:00:00 2001 From: Ed Costello Date: Wed, 8 Aug 2012 13:01:55 -0400 Subject: [PATCH] Address DOCS-385 by adding an explicit warning about recovery of a replica set member --- .../recover-data-following-unexpected-shutdown.txt | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/source/tutorial/recover-data-following-unexpected-shutdown.txt b/source/tutorial/recover-data-following-unexpected-shutdown.txt index dd678ca335f..18c2c286d7e 100644 --- a/source/tutorial/recover-data-following-unexpected-shutdown.txt +++ b/source/tutorial/recover-data-following-unexpected-shutdown.txt @@ -12,7 +12,7 @@ To prevent data inconsistency and corruption, always shut down the database cleanly, and use the :ref:`durability journaling `. The journal writes data to disk every 100 milliseconds by default, and ensures that MongoDB will be able to -recover a constant state even in the case of an unclean shutdown due to +recover to a consistent state even in the case of an unclean shutdown due to power loss or other system failure. If you do not have journaling enabled, use the following procedure to @@ -27,6 +27,13 @@ recover data that may be in an inconsistent state. "Control-C" (when running :program:`mongod` in interactive mode,) or ``kill $(pidof mongod)`` or ``kill -2 $(pidof mongod)``. +.. warning:: Recovering a member of a replica set + + Do not use this procedure to recover a member of a :term:`replica set`. + Instead you should either restore from a :doc:`backup ` + or re-sync from an intact member of the set. + + Process -------