[SERVER-3849] reIndex on secondary fails removing all indexes Created: 14/Sep/11  Updated: 15/Sep/11  Resolved: 15/Sep/11

Status: Closed
Project: Core Server
Component/s: Index Maintenance, Replication
Affects Version/s: 2.0.0
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Tony Hannan Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Participants:

 Description   

Shell:
SECONDARY> rs.slaveOk()
SECONDARY> db.foo.getIndexes()
[
{
"v" : 1,
"key" :

{ "_id" : 1 }

,
"ns" : "test.foo",
"name" : "id"
},
{
"v" : 0,
"key" :

{ "x" : 1, "y" : 1 }

,
"ns" : "test.foo",
"name" : "x_1_y_1"
}
]
SECONDARY> db.foo.reIndex()
{
"nIndexesWas" : 2,
"msg" : "indexes dropped for collection",
"errmsg" : "exception: no index name specified",
"code" : 12523,
"ok" : 0
}
SECONDARY> db.foo.getIndexes()
[ ]

Secondary server log:
Wed Sep 14 10:05:59 [conn5] CMD: reIndex test.foo
Wed Sep 14 10:05:59 [conn5] assertion 13435 not master and slaveok=false ns:test.system.indexes query:

{ ns: "test.foo" }

 Comments   
Comment by Eliot Horowitz (Inactive) [ 15/Sep/11 ]

See SERVER-3866

Generated at Thu Feb 08 03:04:14 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.