Hi,
Yeah, large heap can be problematic like that. :)
But if there is some sort of a leak, and if I had to bet I'd put my money
on your custom QP knowing what I know about this situation, you could also
start Solr with a much smaller heap and grab the heap snapshot as soon as
you see some number o
We do have a custom query parser that is responsible for expanding the user
input query into a bunch of prefix, phrase and regular boolean queries in a
manner similar to that done by DisMax.
Analyzing heap with jhat/YourKit is on my list of things to do but I
haven't gotten around to doing it yet.
Hi,
I've never seen this. You don't have a custom query parser or anything
else custom, do you?
Have you tried dumping and analyzing heap? YourKit has a 7 day eval, or
you can use things like jhat, which may be included on your machine already
(see http://docs.oracle.com/javase/6/docs/technotes/
