From 7fd0b8dfcead97f1a5cc6cebd9b15157a22b4369 Mon Sep 17 00:00:00 2001 From: Tyler Brock Date: Thu, 15 Mar 2012 08:32:25 -0400 Subject: [PATCH] minor: update for replica set docs --- docs/REPLICA_SETS.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/REPLICA_SETS.md b/docs/REPLICA_SETS.md index c401e9f..4a9f3c4 100644 --- a/docs/REPLICA_SETS.md +++ b/docs/REPLICA_SETS.md @@ -41,8 +41,8 @@ the state of any secondary node, the automated refresh will ensure that this sta There are two secenarios in which refresh is helpful and does not raise exceptions: -# You add a new secondary node to an existing replica set -# You remove an unused secondary from an existing replica set +1. You add a new secondary node to an existing replica set +2. You remove an unused secondary from an existing replica set If using MongoDB earlier than 2.0 any changes to replica set state will raise exceptions therefore refresh mode will not be useful.