[SERVER-6292] MongoD server crashes after inserted about 10GB worth of data with "Assertion failure a <= 512*1024*1024 util/alignedbuilder.cpp" Created: 03/Jul/12 Updated: 08/Mar/13 Resolved: 27/Nov/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | GridFS, Internal Code, Usability |
| Affects Version/s: | 2.0.6 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Jose Sebastian Battig | Assignee: | Mathias Stearn |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | SERVER_V2, Windows, crash, insert, performance, update | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Windows 2008 64 bits R2 |
||
| Attachments: |
|
| Operating System: | Windows |
| Participants: |
| Description |
|
I'm running a test, based on gridfs_test.c test_large(). If I run the test once with my configuration, which will create the file twice on the DB with a deletion in between, when is trying to create the file on the second part after deleting the first file it will crash. This happens right away, no waits or nothing. I have attached MongoDConsole.JPG. It shows the warning before the server crashes. See attachment MongoDConsole_3.jpg. That's after another run. The previous run succeeded, so I started the test again. Got the warning more or less right away, and right after that the Journal processor got rid of a lot of journal files, it seems things stabilized there. On this run. I got the warning again, and I'm letting the system run to see if I can get it to crash. Launched the test again, but this time decided not to intervene and let the program run even if getting the warning. Got it right away after the process started, and a little while after got the kiss of death. Warning and crash (see MongoDConsole_crash.jpg). This definitively seems to be a problem with rate of IO. I do think MongoD should be smart enough to "throttle" the client who is pushing data, as the client has no way of knowing this is going on at the MongoD side. |
| Comments |
| Comment by Mathias Stearn [ 05/Jul/12 ] |
|
FYI, GridFS intentionally doesn't support modifying files in-place, so if you plan on doing that I'd advise against using the standard fs.files/fs.chunks as many tools will not be expecting it. That said, this should definitely not cause the error you are seeing. In order to narrow down the cause here, do you know which of the four test_* functions is causing the crash? |
| Comment by Jose Sebastian Battig [ 03/Jul/12 ] |
|
I did a test now launching mongod with option --journalCommitInterval 5 and then using WriteConcern with j = 1, and the performance is more acceptable. |
| Comment by Jose Sebastian Battig [ 03/Jul/12 ] |
|
I added the following code as soon as I connect to the server: mongo_write_concern_init(&wc); And then the problem doesn't appear anymore. The problem is that general operation of the server seems really slow... |