I guess it could be many things.
Typically an easy one to spot is if you have insufficient heap (i.e.
your 16Gb) and the jvm is full gc'ing constantly and not freeing up any
memory and using lots of cpu. This would make solr slow and "hangs up"
as well during potentially long gc pauses.
add:
Hi,
Is there a way to reset the stats counters? For example in the Query
handler avgTimePerRequest is not much use after a while as it is an avg
since the server started.
When putting the data into a monitoring system like nagios it would be
useful to be able to sample the data and reset it
Hi,
We currently are storing all of our data in sql database and use solr
for indexing. We get a list of id's from solr and retrieve the data from
the db.
We are considering storing all the data in solr to simplify
administration and remove any synchronisation and are considering the
follow
according to the wiki you could avoid having 3 filter queries cached by
putting multiple fq parameters:
"Given the following three filtering scenarios of (a) x:bla, (b) y:blub,
and (c) x:bla AND y:blub, will I end up with two or three distinct
filters? In other words, may filters be composites or
add these to your JAVA_OPTS when you start your jvm.
-verbose:gc -XX:+PrintGCTimeStamps -XX:+PrintGCDetails
-Xloggc:/your/path/verbose-gc.log
tail the verbose gc log to see if the timing of your pause corresponds
with a full gc.
On 15/01/10 03:59, Jerome L Quinn wrote:
Is this related to GC
te:
wow! exactly what i'm looking for. What solr1.4 book is this?
thanks so much. If anybody knows the details of how to use this I'd love to
hear your tips, experiences, or comments.
-mike
On Dec 9, 2009, at 12:55 PM, Andre Parodi wrote:
the solr 1.4 book says you can do
the solr 1.4 book says you can do this.
usages of mlt:
"As a request handler with an external input document: What if you want
similarity results based on something that isn't in the index? A final
option that Solr supports is returning MLT results based on text data
sent to the MLT handler (