[DOCS-706] Initial sync of a 1.8.4 secondary can copy v:1 indexes which it cannot use Created: 31/Oct/12 Updated: 29/Nov/12 Resolved: 01/Nov/12 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Shaun Verch | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 11 years, 16 weeks ago | ||||||||
| Description |
|
After syncing a 1.8.4 node from a 2.0.5 node, we get the following result: testreplset:PRIMARY> db.foo.getIndexes() , , Add a note to http://www.mongodb.org/display/DOCS/Index+Versions that this is another situation that requires reindexing, as 1.8.4 cannot use the new indexes. |