From c648260cffaf4fca2e6aa8526fdc7879880f7c29 Mon Sep 17 00:00:00 2001 From: Greg Studer Date: Tue, 12 Feb 2013 10:59:59 -0500 Subject: [PATCH] Update source/release-notes/2.4-upgrade.txt QA testing by mike - he seemed to think this was confusing as written and implied that only mongos processes needed to be upgraded --- source/release-notes/2.4-upgrade.txt | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/source/release-notes/2.4-upgrade.txt b/source/release-notes/2.4-upgrade.txt index 268c8bb7bfa..0135e70df5e 100644 --- a/source/release-notes/2.4-upgrade.txt +++ b/source/release-notes/2.4-upgrade.txt @@ -47,10 +47,10 @@ procedure. :term:`sharded cluster`, as described in :ref:`sharding-balancing-disable-temporally`. -#. Ensure there are no MongoDB processes running 2.0 still active in the - sharded cluster. The automated upgrade process checks this, but - network availability can prevent a definitive check. Wait 5 minutes - after stopping version 2.0 :program:`mongos` processes to confirm +#. Ensure there are no version 2.0 :program:`mongod` or :program:`mongos` + processes still active in the sharded cluster. The automated upgrade process checks this, but + network availability can prevent a definitive check. Wait 5 minutes + after stopping or upgrading version 2.0 :program:`mongos` processes to confirm that none are still active. #. Start a single 2.4 :program:`mongos` process with