[SERVER-15338] collection lacks unique index on _id Created: 20/Sep/14  Updated: 16/Nov/21  Resolved: 14/Nov/14

Status: Closed
Project: Core Server
Component/s: MapReduce
Affects Version/s: 2.6.3
Fix Version/s: None

Type: Question Priority: Major - P3
Reporter: Saurabh Malani Assignee: Ramon Fernandez Marina
Resolution: Incomplete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Participants:

 Description   

while starting up the mongo shell I am getting warnings for four collections which may be a result of a failure few hours back on my primary server. It went down and I had to restart mongo service to bring it back. After doing some research online I figured we can delete this temporary collection created by map reduce.
But when i do a search for them in the mongo shell I am not able to find any results. So I would like to know if they exist then where can I view them or delete them and if they don't then why am I getting such warnings?

PFB logs

 [initandlisten] WARNING: the collection 'db.tmp.mr.coll_9363_inc' lacks a unique index on _id. This index is needed for replication to function properly
 [initandlisten]     To fix this, you need to create a unique index on _id. See http://dochub.mongodb.org/core/build-replica-set-indexes
 [initandlisten] WARNING: the collection 'db.tmp.mr.coll_9362_inc' lacks a unique index on _id. This index is needed for replication to function properly
 [initandlisten]     To fix this, you need to create a unique index on _id. See http://dochub.mongodb.org/core/build-replica-set-indexes
 [initandlisten] WARNING: the collection 'db.tmp.mr.coll_9361_inc' lacks a unique index on _id. This index is needed for replication to function properly
 [initandlisten]     To fix this, you need to create a unique index on _id. See http://dochub.mongodb.org/core/build-replica-set-indexes
 [initandlisten] WARNING: the collection 'db.tmp.mr.coll_9364_inc' lacks a unique index on _id. This index is needed for replication to function properly
[initandlisten]     To fix this, you need to create a unique index on _id. See http://dochub.mongodb.org/core/build-replica-set-indexes

I tried searching on mongo shell using

db.system.namespaces.find({name: '/mr/'})

got no results



 Comments   
Comment by Ramon Fernandez Marina [ 14/Nov/14 ]

saurabh.malani@delhivery.com, we haven't heard back from you for some time so we're going to resolve this ticket. If this is still an issue for you feel free to reopen this ticket and let us know if you would be able to share your dbfiles with us so we can investigate.

Regards,
Ramón.

Comment by Ramon Fernandez Marina [ 28/Oct/14 ]

saurabh.malani@delhivery.com, we haven't heard back from you for a while. If this is still an issue for you, would you consider uploading your database files so we can investigate further?

Thanks,
Ramón.

Comment by Ramon Fernandez Marina [ 23/Sep/14 ]

sat2050, would you be able to share your db files with us so we can investigate the root cause? Let me know, and I can provide a private location for you to upload.

Thanks,
Ramón.

Comment by Saurabh Malani [ 23/Sep/14 ]

2.6.3

Comment by J Rassi [ 22/Sep/14 ]

Could you confirm which version of MongoDB you are running in this cluster?

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