[SERVER-29841] Unable to restore system.indexes in mongo 3.4 Created: 23/Jun/17  Updated: 26/Jun/17  Resolved: 26/Jun/17

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

Type: Question Priority: Major - P3
Reporter: Karthik koganti Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Microsoft Word Mongo new instance errors with system.indexes.docx    
Participants:

 Description   

Hi Team, I have restored complete database from mongo 2.6.6 to mongodb 3.4.5, when we migrate 3.0 database completed database is recovered same as earlier version. As the schema changed from 3.2 and 3.4. The database path file are scatted as collections and indexes but not in folder structure.

We used mongodump and mongorestore commands for dump and restore the database

But when I see the database from Robomongo, it show solder sturcture but missing system.indexes. We are unable to import this file name starting with system.
when we try to create indexes, system throws duplicate record
Attached the screen shots in word document.
Please guide us in the update of servers.



 Comments   
Comment by Stennie Steneker (Inactive) [ 26/Jun/17 ]

Hi Karthik,

Since you have migrated using mongodump and mongorestore from MongoDB 2.6.6 (MMAP storage engine) to MongoDB 3.4.5 (WiredTiger storage engine by default), there are some expected differences in file structure and driver compatibility. The Release Notes section in the MongoDB manual includes a full list of new features and compatibility changes to be aware of for each major release. In particular, you will need to upgrade your MongoDB driver and tools if you want full support for newer MongoDB features.

If Robomongo (now Robo 3T) isn't showing all collections and indexes, you are likely using an older version which does not have full support for the WiredTiger storage engine and MongoDB 3.4. For a quick check I would try connecting to your deployment using the v3.4.5 mongo shell and check your indexes with db.collection.getIndexes() for the collection in question. I also encourage you to try the latest version of Robo 3T or a more actively maintained tool like MongoDB Compass.

Please note that SERVER project is for reporting bugs or feature suggestions for the MongoDB server. For MongoDB-related support discussion please post on the mongodb-user group or Stack Overflow with the mongodb tag. A question like this involving more discussion would be best posted on the mongodb-user group.

Regards,
Stephen

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