[SERVER-28730] Out of memory error when dumping the database Created: 11/Apr/17  Updated: 21/Jun/17  Resolved: 22/May/17

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

Type: Bug Priority: Major - P3
Reporter: Jan S. Assignee: Mark Agarunov
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

ubuntu1604 x86_64


Operating System: ALL
Steps To Reproduce:

On a remote computer I execute:
mongodump.exe /gzip /authenticationDatabase:admin /host myhost /u my-user /p my-password /j 5 /out:E:\DB-Dump

Participants:

 Description   

As suggested by Thomas Schubert in #SERVER-24709 I have created a separate issue:

I am trying to create a complete dump of my database. This always fails after some hours because of a memory problem. The database to be dumped contains 3 large collections with documents of all size and grid.fs files of all size.

The crash does happen approximately after the same run-time - usually when the gzipped bson dump is between 600 and 650GiB.

The storage engine I use is MMAPv1.

db version v3.4.3
git version: f07437fb5a6cca07c10bafa78365456eb1d6d5e1
OpenSSL version: OpenSSL 1.0.2g 1 Mar 2016
allocator: tcmalloc
modules: none
build environment:
distmod: ubuntu1604
distarch: x86_64
target_arch: x86_64

The VM has 3.9GB RAM. While dumping the database no other database operations were running. The system has 2GB (nearly unused) swap.

I a second try I changed the OOM settings of Ubuntu which ended up that I had to reboot the complete VM because Mongo did consume every single bit of memory - even a local logon session was immediately killed by the OOM. Even stopping the dump process did not recover the VM.

I have collected logs and diagnostic data with enabled heapProfilingEnabled=true. Where should I upload them?



 Comments   
Comment by Mark Agarunov [ 22/May/17 ]

Hello mango,

Thank you for providing this information. After looking over this, I do not see anything to indicate a bug in 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.

Thanks,
Mark

Comment by Jan S. [ 11/Apr/17 ]

Ok, logs has been uploaded. Hope this helps you to understand the problem.

Comment by Kelsey Schubert [ 11/Apr/17 ]

Hi mango,

Thank you for opening a new ticket. I've created a secure upload portal for you to use. Would you please also provide the syslog?

Thanks again for your help,
Thomas

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