[SERVER-8125] Text search with large result set raises unhandled exception Created: 09/Jan/13 Updated: 11/Jul/16 Resolved: 23/Jan/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Text Search |
| Affects Version/s: | None |
| Fix Version/s: | 2.4.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | J Rassi | Assignee: | Eliot Horowitz (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
Works as designed?
|
| Comments |
| Comment by Ben Becker [ 23/Jan/13 ] | |||||||||||||||||||||||||||||||||
|
Moved v8 issue to | |||||||||||||||||||||||||||||||||
| Comment by Ben Becker [ 23/Jan/13 ] | |||||||||||||||||||||||||||||||||
|
One work-around is to remove (or significantly increase) the resource limits we set for each isolate. In a local test, the mongo client uses ~750mb of resident memory when resource constraints are lifted. gc() reduces consumption to 112mb (much higher than the 10.1mb we start with). Seems like we're allocating too much memory, and GC isn't freeing everything it can, even after multiple runs. | |||||||||||||||||||||||||||||||||
| Comment by J Rassi [ 22/Jan/13 ] | |||||||||||||||||||||||||||||||||
|
Mmm, I linked to The above run was with "2.3.2-pre" (the shell doesn't get more specific with the release number). Here's another run with 4c8fe4f520c872cb6bc5cefd3b0ab10cd9fc1b43 (build from today), pretty much the same, but posting again below in case the updated stack trace is helpful. Note the setup for reproducing this is pretty simple (just need to run mongod --setParameter textSearchEnabled=true) with 2.3.2+.
| |||||||||||||||||||||||||||||||||
| Comment by Ben Becker [ 22/Jan/13 ] | |||||||||||||||||||||||||||||||||
|
rassi@10gen.com, thanks. I don't think this bug is related to Also, could you post the version of the shell? | |||||||||||||||||||||||||||||||||
| Comment by J Rassi [ 22/Jan/13 ] | |||||||||||||||||||||||||||||||||
|
Looks like 15,817,862 bytes, see below:
| |||||||||||||||||||||||||||||||||
| Comment by Ben Becker [ 22/Jan/13 ] | |||||||||||||||||||||||||||||||||
|
rassi@10gen.com, do you know how large the result set should have been in the case where V8 reported OOM? | |||||||||||||||||||||||||||||||||
| Comment by J Rassi [ 22/Jan/13 ] | |||||||||||||||||||||||||||||||||
|
Note that the example in the description now unfortunately fails with a less nice error message (see below) in the shell due to a V8-related issue ( eliot: I'm leaving this closed for now, but note that if this needs to be done for 2.4 then we need to either fix
| |||||||||||||||||||||||||||||||||
| Comment by auto [ 14/Jan/13 ] | |||||||||||||||||||||||||||||||||
|
Author: {u'date': u'2013-01-14T16:07:20Z', u'email': u'eliot@10gen.com', u'name': u'Eliot Horowitz'}Message: | |||||||||||||||||||||||||||||||||
| Comment by Eliot Horowitz (Inactive) [ 09/Jan/13 ] | |||||||||||||||||||||||||||||||||
|
Should error, but need a nicer error message. |