[SERVER-24894] mongodump utility command takes forever. Created: 05/Jul/16  Updated: 08/Aug/16  Resolved: 08/Aug/16

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

Type: Bug Priority: Major - P3
Reporter: Renu Sahukara Assignee: Unassigned
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Steps To Reproduce:

use meantest
db.createCollection("tech")
db.tech.insert(
    [
        {
            name: "MongoDB",
            role: "Database",
            language: "JavaScrip"
        },
        {
            name: "Express",
            role: "Web application server",
            language: "JavaScrip"
        },
        {
            name: "Angular",
            role: "Front-end framework",
            language: "JavaScrip"
        },
        {
            name: "Node.js",
            role: "Platform",
            language: "JavaScrip"
        }
    ]
)

In a separate cmd shell window, I ran "mongodump --db meantest". Took more than 4 hours, and showed no sign of it ever completing.

Tried "mongodump --db meantest --gzip". It's been 2.5 hours and counting, with no signs of getting completed. What am I doing wrong?

I use the latest version of mongodb as of today, on my x64 windows 10 home edition.

Participants:

 Description   

I have just tried out MongoDB. All I have is a small collection of just 4 documents. I tried using the mongodump utility on my database. It runs for ever.



 Comments   
Comment by Kelsey Schubert [ 08/Aug/16 ]

Hi renu318,

Unfortunately, we have not been able to reproduce this issue. For MongoDB-related support discussion please post on the mongodb-users group or Stack Overflow with the mongodb tag. A question like this involving more discussion would be best posted on the mongodb-users group.

Kind regards,
Thomas

Comment by Renu Sahukara [ 05/Jul/16 ]

I started mongod, and then did this.

mongodump --db meantest -vvv

Same thing, it just stays.. no logs, no verbosity..

Comment by Renu Sahukara [ 05/Jul/16 ]

Oh, I will try with the vvv increased verbosity arguments. Sorry, I didn;t notice.

Regards.

Comment by Renu Sahukara [ 05/Jul/16 ]

I tried things (that I'm afraid are lame) after it was taking for ever,

I closed the shell windows, uninstalled MongoDB, deleted the data folder, restarted, installed it again, created the data folder.. did the same things and tried mongodump.
This time without the mongod server running.

I expected it would throw an error like "mongod instance not running".
But instead, the cursor just went to the next line in the shell and blinked indefinitely. There was absolutely no sign if it was doing anything at all.
(Do you think I should just give up and use free db space provided on mlabs?)

Comment by Renu Sahukara [ 05/Jul/16 ]

It just goes to the next line and the cursor blinks forever. It doesn't output any inline message on the shell.. (nada). I can show you a screenshot of it if you want..

Comment by Michael O'Brien [ 05/Jul/16 ]

Renu,
When you run mongodump in your shell, it should write some log output inline describing its progress, can you copy/paste that output here?

Comment by Renu Sahukara [ 05/Jul/16 ]

HI Michael,
Thanks for the quick reply. I can't find the log file.

This is pretty much what I did chronologically..
I ran the msi installer and then MongoDB was installed in C:\Program Files

Then I ran mongod and saw that it yelled.. "no directory found at C:\data\db" or something of that sort.
Assumed, that's where it's supposed to put it's db files. I manually created the folder C:\data\db and ran mongod again. This time, the db server started.

Then in a separate cmd shell, I ran mongo and created my db, and collections, and played with the collection for a bit.

Then I tried the mongodump utility.

I can't find the log file in the MongoDB installation directory or the C:\data\db directory.

I know I did something wrong, or may be I'm not looking at the right places.
Hope you can help me sort out the issue.

Regards.

Comment by Michael O'Brien [ 05/Jul/16 ]

Hi Renu,
Can you show a sample of the log output from mongodump while it's running? And also try with increased verbosity level by adding -vvv to the command line args?
Are there any other collections in the "meantest" db that are being dumped when you run mongodump?

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