Lab - Importing a Dataset - wrong hash?

MongoDB University M103: Basic Cluster Administration
#1

Hi All,

I believe I have completed the final lab and having run the validate, I have received a hash, but when I submit that I get the incorrect message.

Unfortunately, I don’t have any error messages to go on so I am not sure how to approach troubleshooting. Below is the output I received, I have not included the command/hash as I guess that is kind of the answer.

Any pointers appreciated: +1:

Terminal Output:

2019-09-23T16:27:02.866+0000 no collection specified
2019-09-23T16:27:02.866+0000 using filename ‘products’ as collection
2019-09-23T16:27:02.877+0000 connected to: localhost:27000
2019-09-23T16:27:05.868+0000 [######…] applicationData.products 23.1MB/87.9MB (26.2%)
2019-09-23T16:27:08.869+0000 [############…] applicationData.products 45.2MB/87.9MB (51.4%)
2019-09-23T16:27:11.868+0000 [##################…] applicationData.products 67.2MB/87.9MB (76.4%)
2019-09-23T16:27:14.554+0000 [########################] applicationData.products 87.9MB/87.9MB (100.0%)
2019-09-23T16:27:14.557+0000 imported 516784 documents

#2

Hi @Daniel_88997,

Can you please share the “mongoimport” command that you are using to load the dataset to help us debug the issue better?

Meanwhile, please check and confirm if you are following the lab instructions exactly as mentioned, i.e. the application username, etc.

Thanks,
Muskan
Curriculum Support Engineer

#3

Hi Muskan,

Thanks for your response.

Mongo import used:

vagrant@m103:~$ mongoimport --port 27000 --username=m103-application-user --password=m103-application-pass --authenticationDatabase=admin --db=applicationData --collection=products /shared/products.json

I moved the the product file from dataset to shared … before I realised both folders were available in the VM.

I believe I have used the right information - I have reviewed the directions many times but can’t see my error. Hope its not something silly :slight_smile:

Regards

DB

#4

Hi @Daniel_88997,

The command used here looks good to me.

Can you please try to re-launch your mongod process, authenticate the user on applicationData database and then drop and reload your dataset?

Make sure you use the right validation script - validate_lab_import_dataset

Let me know if you face the same issue again.

Thanks,
Muskan
Curriculum Support Engineer

#5

do I have a user that is allowed to drop … the user created only has read/write so I’m getting an error (using Compass):

not authorized on applicationData to execute command { dropDatabase: 1, lsid: { id: UUID(“adf19d0a-6a67-41a4-b5c0-c0ac7ed93227”) }, $db: “applicationData” }

Thanks

#6

Thanks Muskan,

I dropped the Collections (there were 2) instead of the database and that allowed me to run the import.

I think somehow I had created/imported a second Collection that was not meant to be there … im not sure how?

Anyway the new hash was successful :+1:

1 Like
#7