Major - P3
Resolution: Works as Designed
I’m having problems using mongoDB with high load.
The database has about 7200 collections, storing documents in different interval of time; every 1 sec in some cases, every 1 min in other. Each document is composed as
Each iteration, the application sends all the information to the database; there is no incomplete documents.
When I start using the application and requesting data, in several times, Mongo returns AssertionException, with code 0 and the following message
According what I found, this message means that the cursor is not longer valid, it’s timed out. I configure the timeout when connecting with mongo server. At the beginning, the timeout was 60 secs. I increased it to 90 secs but it stills returns this error. I even tried to disabled the timeout.
Each request is handled by different threads
With low load, even returning these errors, everything keeps running. With high load, randomly, my server stops working on a request for data to some collection (not always the same).
These errors started when we upgraded to mongo 3; I tested mongo 3.0.7, 3.2.0, 3.2.7 and 3.3.8, and the behavior was the same in all cases.
In the Windows Event viewer, the error is
Faulting application name: app.exe, version: 0.0.0.0, time stamp: 0x5758321a
Faulting module name: mongoclient.dll, version: 0.0.0.0, time stamp: 0x5761d4aa
Exception code: 0xc0000005
Fault offset: 0x00000000000e1f0d
Faulting process id: 0x44d4
Faulting application start time: 0x01d1cbfea9b06353
Faulting application path: C:\Program Files\MyApp\App\app.exe
Faulting module path: C:\Program Files\MyApp\App\mongoclient.dll
Report Id: 2d0ad6f9-37f4-11e6-babf-0aa31160729b
Windows Server 2008 R2 64 bits.
RAM: 15 GB
Mongo C++ legacy driver 1.1.1, compiled with Visual Studio 2010 and boost 1.60.0.
MongoDB running at localhost, with no replica
Can anyone help me?