Skip to content

minor update to creating index on sharded cluster #85

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
Jul 24, 2012
Merged

minor update to creating index on sharded cluster #85

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
7 changes: 3 additions & 4 deletions source/administration/indexes.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -265,10 +265,9 @@ on :term:`secondary` members of replica sets. The foreground index
building process blocks all replication and read operations on the
secondaries while they build the index.

Secondaries will only begin building indexes *after* the
:term:`primary` finishes building the index. All secondaries will
build indexes at the same time. In :term:`sharded clusters <shard
cluster>`, the :program:`mongos` will send :func:`ensureIndex()
Secondaries will begin building indexes *after* the
:term:`primary` finishes building the index. In :term:`sharded clusters
<shard cluster>`, the :program:`mongos` will send :func:`ensureIndex()
<db.collection.ensureIndex()>` to the primary members of the replica
set for each shard, which then replicate to the secondaries after the
primary finishes building the index.
Expand Down