[DOCS-4579] Impact and behaviour of index rebuilding in a v2.4 replica set Created: 23/Dec/14  Updated: 27/Jul/16  Resolved: 27/Jul/16

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: None
Fix Version/s: mongodb-2.6

Type: Task Priority: Major - P3
Reporter: Luke Prochazka Assignee: Unassigned
Resolution: Won't Fix Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Participants:
Days since reply: 9 years, 8 weeks, 2 days ago

 Description   

In this DOCS reference: http://docs.mongodb.org/v2.4/core/index-creation/

Please amend the DOC to add clarity on index build behaviour, in particular the following statements:

In version 2.4, a foreground index build is default, when complete on a replica set primary, it'll replicate to the secondaries with a foreground build task (regardless if the primary was issued a foreground or background index option). The replication worker will take a global DB lock, which will queue reads and writes to all DBs on that server.


Generated at Thu Feb 08 07:48:21 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.