I am running version 3.4 of mongo on a Windows 2012 R2 server using the default storage mechanism (Wired Tiger). Mongod runs as a Windows service.
Unfortunately, the service occasionally suppresses the "out of memory" error. this is from the mongologist:
2017-05-14T22:34:15.888+0000 I CONTROL [ftdc] mongod.exe
...\src\mongo\util\stacktrace_windows.cpp(239)
mongo::printStackTrace+0x43
2017-05-14T22:34:15.888+0000 I CONTROL [ftdc] mongod.exe
???
2017-05-14T22:34:15.896+0000 I CONTROL [ftdc] mongod.exe
...\src\mongo\util\allocator.cpp(51) ???
2017-05-14T22:34:15.896+0000 I CONTROL [ftdc] mongod.exe
???
2017-05-14T22:34:15.896+0000 I CONTROL [ftdc] mongod.exe
???
2017-05-14T22:34:15.896+0000 I CONTROL [ftdc] mongod.exe
???
2017-05-14T22:34:15.896+0000 I CONTROL [ftdc] mongod.exe
???
2017-05-14T22:34:15.896+0000 I CONTROL [ftdc] mongod.exe
???
2017-05-14T22:34:15.896+0000 I CONTROL [ftdc] mongod.exe
???
2017-05-14T22:34:15.896+0000 I CONTROL [ftdc] mongod.exe
???
2017-05-14T22:34:15.902+0000 I CONTROL [ftdc] ucrtbase.DLL
crt_at_quick_exit+0x7d
2017-05-14T22:34:15.902+0000 I CONTROL [ftdc] KERNEL32.DLL
BaseThreadInitThunk+0x22
2017-05-14T22:34:15.902+0000 F - [ftdc] out of memory.
After some research, people suggest limiting memory usage:
- , Linux "unlimit", MongoDB:
- Windows?
- ?
- ?
!