[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:
Duplicate
duplicates DOCS-654 Migrate Index Versions Doc Closed
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()
[
{
"name" : "id",
"ns" : "test.foo",
"key" :

{ "_id" : 1 }

,
"v" : 0
},
{
"v" : 1,
"key" :

{ "x" : 1 }

,
"ns" : "test.foo",
"name" : "x_1"
}
]
testreplset:PRIMARY> db.serverStatus().version
1.8.4
testreplset:PRIMARY>

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.


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