From 5e336efa0fd284add762b26f7a4ea0dbcf0dd76a Mon Sep 17 00:00:00 2001 From: Nicholas Tang Date: Tue, 19 Mar 2013 15:48:00 -0300 Subject: [PATCH] Update 2.4-upgrade.txt MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Fixed text - referenced 2.0 when it should've said 2.2. (Side question, maybe worth a DOCS ticket: should we have instructions for going from 2.0 -> 2.4?  Or just let users do the two-step from 2.0 -> 2.4?) --- source/release-notes/2.4-upgrade.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/release-notes/2.4-upgrade.txt b/source/release-notes/2.4-upgrade.txt index 9e949d5a22f..57f75ad67da 100644 --- a/source/release-notes/2.4-upgrade.txt +++ b/source/release-notes/2.4-upgrade.txt @@ -60,7 +60,7 @@ other members are available to minimize downtime. Use the following procedure: #. Upgrade the :term:`secondary` members of the set one at a time by - shutting down the :program:`mongod` and replacing the 2.0 binary + shutting down the :program:`mongod` and replacing the 2.2 binary with the 2.4 binary. After upgrading a :program:`mongod` instance, wait for the member to recover to ``SECONDARY`` state before upgrading the next instance.