[SERVER-8721] Secondaries with {textSearchEnabled:false} will build text indexes, but won't perform text searches Created: 25/Feb/13 Updated: 08/Mar/13 Resolved: 26/Feb/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication, Text Search |
| Affects Version/s: | 2.4.0-rc1 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | J Rassi | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
(Filing on behalf of milkie) The procedure that we document for enabling text search on sharded/replicated clusters is to set {textSearchEnabled:true}on every mongos and mongod. Consider the following failure scenario, in which the user does not follow the documented instructions: 1. User enables text search on mongos and their primaries, but forgets to enable it on their secondaries Suggested fix: force secondaries to fail at index build time if they do not have text search enabled. |