From fa7a4c33962c9011cd2c076f487e068d647c3dd0 Mon Sep 17 00:00:00 2001 From: matulef Date: Thu, 6 Dec 2012 17:58:49 -0500 Subject: [PATCH] Update source/release-notes/2.4.txt MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit A CS customer seemed to miss this warning before (see https://jira.mongodb.org/browse/CS-5372 ) so I revised the text to make it a little clearer.  --- source/release-notes/2.4.txt | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/source/release-notes/2.4.txt b/source/release-notes/2.4.txt index 8bbac79d13b..53cb0a00265 100644 --- a/source/release-notes/2.4.txt +++ b/source/release-notes/2.4.txt @@ -365,7 +365,7 @@ key. Consider the following properties when using a hashed shard key: shard or set of shards; however, the :program:`mongos` must route range queries to all shards. -- When using a hashed shard key on a collection without data, MongoDB +- When using a hashed shard key on a new collection, MongoDB automatically pre-splits the range of 64-bit hash values into chunks. By default, the initial number of chunks is equal to twice the number of shards at creation time. You can change the number of @@ -375,6 +375,10 @@ key. Consider the following properties when using a hashed shard key: .. code-block:: javascript db.adminCommand( { shardCollection: "test.collection", key: { a: "hashed"}, numInitialChunks: 2001 } ) + + Note: pre-splitting only occurs when sharding empty collections. The + chunks will not be pre-split when sharding collections that already + have data. .. warning::