[DOCS-1540] Conflicting information about background vs. foreground Created: 24/May/13 Updated: 30/Oct/23 Resolved: 20/Jun/13 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Tricia Mills Gray | Assignee: | Sam Kleinman (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | indexing, replicaset | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Version 2.2.1 |
||
| Participants: | |
| Days since reply: | 10 years, 34 weeks, 6 days ago |
| Description |
|
We are attempting to solve an issue where we need to propagate the indexes on our test environment to our production environment without any loss of availability. The problem is, the documentation that our Dev Lead has gone by reads that indexing on the secondaries turns into a foreground task, which makes that node unavailable: "Build Indexes on Replica Sets Background index creation operations become foreground indexing operations on secondary members of replica sets. The foreground index building process blocks all replication and read operations on the secondaries while they build the index." However, our DB Dev Manager finds another area in the docs that reads something entirely different: "Version 2.1.0 and later Indexes can be built in the foreground or background. Background indexes builds on the primary will result in background index builds on the secondaries. Recovering members (for example, new members who are initial syncing or members in maintenance mode) will always build indexes in the foreground because they cannot handle reads anyway. Generally you want recovering members to catch up as quickly as possible." Can you clear this up for us? This issue has been blocking a very important feature to be released on the live site, and we're trying to get a fix done by EOD tomorrow (5/23/2013). We need to know what to expect so we can forge a solution ASAP. |
| Comments |
| Comment by Sam Kleinman (Inactive) [ 20/Jun/13 ] |
|
this issue is resolved in the current version of the documentation. |
| Comment by Tricia Mills Gray [ 29/May/13 ] |
|
https://wiki.10gen.com/pages/viewpage.action?pageId=41190076 I did a Google search on the text posted above and found this URL referenced. |
| Comment by Scott Hernandez (Inactive) [ 24/May/13 ] |
|
Indexes on secondaries are always built in the foreground, when created via replication. Here are directions on building indexes on a replica set which produces the highest availability: http://docs.mongodb.org/manual/tutorial/build-indexes-on-replica-sets/ What is the url of the page with the confusing/contradictory info? |