From faf0c4d6a94a88efdc9bb36808f7751247041b73 Mon Sep 17 00:00:00 2001 From: Greg Studer Date: Wed, 27 Feb 2013 11:24:15 -0500 Subject: [PATCH] Update source/release-notes/2.4-upgrade.txt for SERVER-8710 --- source/release-notes/2.4-upgrade.txt | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/source/release-notes/2.4-upgrade.txt b/source/release-notes/2.4-upgrade.txt index 4045a8411ee..5d70bedd045 100644 --- a/source/release-notes/2.4-upgrade.txt +++ b/source/release-notes/2.4-upgrade.txt @@ -56,6 +56,11 @@ metadata in any other way. your cluster. 2.0 process may re-introduce old metadata formats into cluster metadata. + Also ensure you have sufficient space available on your config server before + starting the upgrade process. The information added during upgrade + will be only a fraction of the current config data size, but preallocation + of data files may cause suprising effects. See :ref:`what-tools-can-i-use-to-investigate-storage-use-in-mongodb`. + Sharded Cluster Upgrade Procedure ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ @@ -63,8 +68,7 @@ Do not perform operations that modify metadata while performing this procedure. 1. Turn off the :ref:`balancer ` in the - :term:`sharded cluster`, as described in - :ref:`sharding-balancing-disable-temporally`. + :term:`sharded cluster`, as described in`:ref:`sharding-balancing-disable-temporally`. #. Ensure there are no version 2.0 :program:`mongod` or :program:`mongos` processes still active in the sharded