[SERVER-73041] Mongorestore from a 4.2 dump have all index missing Created: 19/Jan/23  Updated: 27/Oct/23  Resolved: 23/Jan/23

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

Type: Bug Priority: Major - P3
Reporter: Daniel Wan Assignee: Yuan Fang
Resolution: Community Answered Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File image-2023-01-19-23-59-52-007.png     PNG File image-2023-01-20-00-00-52-042.png     Text File mongorestore_.pcweb_dev_rs.txt     Text File mongorestore_.pcweb_sit_rs.txt    
Operating System: ALL
Steps To Reproduce:

we try restore from another 4.2.23 database dump to 6.0.3 having the same issue

Participants:

 Description   

We import a 4.2.23 dump to 6.0.3 seems to have all the index missing

4.2.23 dump command

/bin/mongodump -h dehamsl5076.int.kn --port 27017 -u admin -p password -o /data/mongodump/dumps/

 

6.0.3 restore command (we do rename the database from ptp to dev_ptp

time mongorestore --authenticationDatabase=admin -u=admin -p=password -d dev_ptp /data/mongodump/dehamsl5094_dumps/dumps/ptp



 Comments   
Comment by Daniel Wan [ 24/Jan/23 ]

Hi Fang,

 

Thanks for your reply, we do ask in the developer community and there are lot of input and will consider them in our upgrade process.

https://www.mongodb.com/community/forums/t/can-we-do-a-mongo-4-2-dump-and-then-restore-to-mongo-6-0-3-directly/209394

 

Regards,

Daniel Wan

Comment by Yuan Fang [ 23/Jan/23 ]

Hi daniel.wan@kuehne-nagel.com,

Thank you for bringing this issue to our attention. I understand that you were unable to see the index data after attempting to restore a 4.2 dump to a 6.0 MongoDB instance. Based on the log you provided, it appears that the mongorestore failed. Please note that multiple version upgrades it not guaranteed to succeed. In order for this to work, you will need to follow the upgrade path through successive major releases of MongoDB ( 4.2 → 4.4 → 5.0 → 6.0). I have found a thread on the MongoDB development forum that may be of help to you in resolving this issue.

If you have any further questions, we'd like to encourage you to start by asking our community for help by posting on the MongoDB Developer Community Forums. If the discussion there leads you to suspect a bug in the MongoDB server, then we'd want to investigate it as a possible bug here in the SERVER project.

Regards,
Yuan

Comment by Daniel Wan [ 19/Jan/23 ]

4.2 collection purchaseHeader with index

 

6.0.3 collection purchaseHeader restore with no index

Generated at Thu Feb 08 06:23:29 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.