[SERVER-8666] adding large docs to capped collection can fail based on history Created: 22/Feb/13 Updated: 10/Dec/14 Resolved: 16/May/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | 2.2.2 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Denis Shashkov | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
In the version 2.2.2 MAX_LOG_LINE is a constant defined in src/mongo/util/log.cpp:
With profiling enabled, queries with long lines yields assertion:
Of course, it can happen many times at any times. |
| Comments |
| Comment by Adamo Tonete [ 19/Feb/14 ] |
|
Eliot, I have the same problem and my mongod instance is down after this message. I set the profiling level to 2 and after a insert of a object with 93k I received this message. Print: Wed Feb 19 10:51:15.415 [repl writer worker 1] ERROR: warning: log line attempted (93k) over max size(10k), printing beginning and end Wed Feb 19 10:51:15.415 [repl writer worker 1] Fatal Assertion 16360 ***aborting after fassert() failure Wed Feb 19 10:51:15.473 Got signal: 6 (Aborted). In the same document have this error too ( |
| Comment by Eliot Horowitz (Inactive) [ 24/Feb/13 ] |
|
I think what happened here is a bit different. Writing to the profile collection for a totally different reason. |