-
Type: Bug
-
Resolution: Gone away
-
Priority: Critical - P2
-
None
-
Affects Version/s: 4.2.6
-
Component/s: None
-
None
-
Environment:Ubuntu 20
I've mongodumped a very small database (2 collections, <500 documents total) from an Atlas cluster database, and want to restore it in another database on the same cluster. mongorestore doesn't output anything apparently indefinitely, and when I Ctrl+C, it finally fails, but without any actionable error message.
$ mongodump --uri $MONGO_PROD_READONLY --archive=dbrepl.mongodump$ mongodump --uri $MONGO_PROD_READONLY --archive=dbrepl.mongodump2020-05-11T18:52:21.758-0700 writing mydb.users to archive 'dbrepl.mongodump'2020-05-11T18:52:22.141-0700 writing mydb.posts to archive 'dbrepl.mongodump'2020-05-11T18:52:22.294-0700 done dumping mydb.users (384 documents)2020-05-11T18:52:22.367-0700 done dumping mydb.posts (59 documents)$ mongorestore --uri $MONGO_DEV --archive=dbrepl.mongodump2020-05-11T19:11:35.050-0700 preparing collections to restore from2020-05-11T19:11:35.114-0700 finished restoring mydb.users (0 documents, 0 failures)
frozen
^C2020-05-11T19:12:22.582-0700 signal 'interrupt' received; attempting to shut down
frozen again
^C2020-05-11T19:12:24.557-0700 signal 'interrupt' received; forcefully terminating
Without the `–archive` option, mongorestore does display this error message:
$ mongorestore --uri $MONGO_DEV
Failed: mydb.users: error reading database: (AtlasError) user is not allowed to do action [listCollections] on [mydb.]
The $MONGO_DEV referst to a different database, mydb-dev. I'm not sure why mongorestore wants to listCollections on mydb.