I just did some allocation profiling on the stock Solr example... it's
not completely idle when no requests are being made.
There's only one thing allocating memory: org.mortbay.util.Scanner.scanFiles()
That must be Jetty looking to see if any of the files under webapps has changed.
It's really n
Here is exactly half an hour from roughly the beginning of logging. There's
nothing to see really because no requests are sent, you just see the GC
behaviour:
[Full GC 211987K->208493K(432448K), 0.6273480 secs]
[GC 276333K->212269K(438720K), 0.0929710 secs]
[GC 289133K->216269K(439936K), 0.1019780
Please send a log covering at least the 2.5 minutes you discuss, but
upwards of 5 minutes would be good.
On Oct 15, 2009, at 1:26 PM, nonrenewable wrote:
Did I read that right? 330K docs == 12 GB index.
Ops, missed the dot - 1.2GB, but i don't think that should really
make the
differen
>Did I read that right? 330K docs == 12 GB index.
Ops, missed the dot - 1.2GB, but i don't think that should really make the
difference in this case. Even if it was 12 GB it would just have some really
juicy documents, right? :)
>Can you share the Solr logs and/or your config? Is this happenin
On Oct 14, 2009, at 12:26 PM, nonrenewable wrote:
I'm curious why this is occurring and whether i can prevent it. This
is my
scenario:
Locally I have an idle running solr 1.3 service using lucene 2.4.1
which has
an index of ~330K documents containing ~10 fields each(total size
~12GB).
