From b431bda0444dcdecdaa0fd1ccc318b27a2e9b7ea Mon Sep 17 00:00:00 2001 From: Adam C Date: Thu, 3 Jan 2013 15:04:43 +0000 Subject: [PATCH] Update source/reference/command/compact.txt Changed the note about the status change for a compact to be a warning and altered the case of the states to make it more in line with what is actually displayed in rs.status() and added a link to the state definitions for more info. --- source/reference/command/compact.txt | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/source/reference/command/compact.txt b/source/reference/command/compact.txt index cc2f8abaa1d..c4364e90305 100644 --- a/source/reference/command/compact.txt +++ b/source/reference/command/compact.txt @@ -165,13 +165,13 @@ compact ``force:true`` above for information regarding compacting the primary. - - If you run :dbcommand:`compact` on a secondary, the secondary - will enter a "recovering" state to prevent clients from + .. warning:: If you run :dbcommand:`compact` on a secondary, the + secondary will enter a "RECOVERING" state to prevent clients from sending read operations during compaction. Once the compaction - finishes the secondary will automatically return to secondary - state. + finishes the secondary will automatically return to "SECONDARY" + state. See :status:`members.state` for more information on states. - You may refer to the "`partial script for automating step down + - You may refer to the "`partial script for automating step down and compaction `_") for an example.