Skip to content

Update source/release-notes/2.4.txt #456

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Dec 6, 2012
Merged

Update source/release-notes/2.4.txt #456

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion source/release-notes/2.4.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand All @@ -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::

Expand Down