-
Type:
Bug
-
Resolution: Done
-
Priority:
Major - P3
-
None
-
Affects Version/s: 3.0.0
-
Component/s: WiredTiger
-
None
-
ALL
We upgraded to 3.0.0 following the day of release and did a mongorestore to entirely rebuild all of our databases into wiredTiger's engine. It worked well for approximately 4 days of low-level usage before throwing an "out of memory" error during some regular (non-heavy) usage.
It doesn't appear as if this is related to SERVER-16902, as we're talking about less than 100,000 inserts, updates, deletes over several days, and nothing in bulk.
We're configured with 4GB of memory allocated to WT. Snappy compression is on, as is prefixCompression. The machine is virtual and dynamically allocates memory. It appears that the system was only using 8GB out of 12GB of potential memory at the time of crash.
wiredTiger: engineConfig: cacheSizeGB: 4
2015-03-10T16:28:52.007-0500 I WRITE [conn42060] remove Monitoring.RecordSearchIssue ndeleted:53714 keyUpdates:0 writeConflicts:0 numYields:2484 locks:{} 54255ms
2015-03-10T16:28:52.009-0500 I COMMAND [conn42060] command Monitoring.$cmd command: delete { delete: "RecordSearchIssue", writeConcern: { fsync: false, j: true }, ordered: true, deletes: [ { q: {}, limit: 0 } ] } keyUpdates:0 writeConflicts:0 numYields:0 reslen:40 locks:{} 54257ms
2015-03-10T16:28:52.369-0500 I COMMAND [conn42060] command OnspringC1.$cmd command: listCollections { $query: { listCollections: 1 } } keyUpdates:0 writeConflicts:0 numYields:0 reslen:8432 locks:{} 289ms
2015-03-10T16:28:52.648-0500 I CONTROL [conn42060] Stack trace failed, SymInitialize failed with error 3765269347
2015-03-10T16:28:52.648-0500 F - [conn42060] out of memory.
- related to
-
-
- Closed
-