[SERVER-19061] insert data fast, server crash with cannot allocate memory message Created: 20/Jun/15 Updated: 14/Apr/16 Resolved: 21/Jun/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin, WiredTiger |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | THUAN | Assignee: | Ramon Fernandez Marina |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | crash | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Centos 7 |
||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Operating System: | Linux | ||||||||
| Participants: | |||||||||
| Description |
|
| Comments |
| Comment by THUAN [ 23/Jun/15 ] | |||
|
I tried to setting a longer timeout Thanks, | |||
| Comment by Ramon Fernandez Marina [ 22/Jun/15 ] | |||
|
tieutinh189, please note that setting a very low value for cursor timeout may impact your application. Please see this comment for more information. Thanks, | |||
| Comment by Ramon Fernandez Marina [ 21/Jun/15 ] | |||
|
Thanks for getting back to us tieutinh189, and glad to hear the workaround worked for you. This behavior was reported in Regards, | |||
| Comment by THUAN [ 21/Jun/15 ] | |||
|
I have try setting, now, no longer occurred. | |||
| Comment by Ramon Fernandez Marina [ 20/Jun/15 ] | |||
|
Thanks for additional information tieutinh189. The line
indicates you're hitting the 20k session limit, which can be achieved by not properly closing cursors. If you're using the Node.js driver you may want to check Are you using the Node.js driver? Can you please try setting a low value for idle cursors timeout and try your insert workload again?
Thanks, | |||
| Comment by Daniel Pasette (Inactive) [ 20/Jun/15 ] | |||
|
looks like a duplicate of | |||
| Comment by THUAN [ 20/Jun/15 ] | |||
|
Log startup 2015-06-20T20:29:03.087+0700 I CONTROL ***** SERVER RESTARTED ***** , operationProfiling: { mode: "slowOp", slowOpThresholdMs: 100 }, processManagement: { fork: true, pidFilePath: "/var/run/mongodb/mongod.pid" }, security: { authorization: "enabled", keyFile: "/var/key/mongodb_key" }, storage: { dbPath: "/home/data/new", directoryPerDB: true, engine: "wiredTiger" }, systemLog: { destination: "file", logAppend: true, path: "/home/logs/mongodb/mongod.log" }} Thank you | |||
| Comment by Ramon Fernandez Marina [ 20/Jun/15 ] | |||
|
tieutinh189, as per the error in the log MongoDB is not able to allocate memory. Can you please send us:
to further diagnose this issue? Thanks, |