Details
-
Bug
-
Resolution: Done
-
Major - P3
-
None
-
2.6.6
-
None
-
ALL
-
Description
I have some collection that is only used for archiving (no reads). I have removed the _id index at some point (I think it was still in ver 2.4).
Then, I started the process of upgrading to a replica set from single instance. When I connect to mongo I get the following message:
015-01-05T10:08:39.088+0000 [initandlisten] WARNING: the collection 'stats.invalid_events' lacks a unique index on _id. This index is needed for replication to function properly
|
2015-01-05T10:08:39.088+0000 [initandlisten] To fix this, you need to create a unique index on _id. See http://dochub.mongodb.org/core/build-replica-set-indexes
|
I created an index, but the warning still appears:
rs1-test:PRIMARY> db.invalid_events.getIndexes()
|
[
|
{
|
"v" : 1,
|
"unique" : true,
|
"key" : {
|
"_id" : 1
|
},
|
"name" : "_id_",
|
"ns" : "stats.invalid_events",
|
"background" : true
|
}
|
]
|