Hi,
EmbeddedSolrServer bypass the servlet container.
Please see :
http://find.searchhub.org/document/a88f669d38513a76
On Thursday, May 19, 2016 6:23 PM, Roman Slavik wrote:
Hi Ahmet,
thanks for your response, I appreciate it.
I thought that EmbeddedSolrServer is just wrapper around Solr cor
Hi Ahmet,
thanks for your response, I appreciate it.
I thought that EmbeddedSolrServer is just wrapper around Solr core
functionality. Solr 4.7.2 is (was?) distributed as war file and I didn't
found any mention about compatibility problem with Tomcat.
Maybe with jetty it would work slightly faste
Hi,
thanks for your response!
We use javamelody for some basic statistics about app. Here are some graphs
from last 24 hours:
http://imgur.com/a/OQxnb
First graph is memory used by application. Second graph shows how seach
time rapidly increased.
At 13:40 there was neccessary app restart and at 1
Hi Roman,
You said you were using EmbeddedSolrServer, also you mention Tomcat.
I don't think it is healthy to use both.
Also I wouldn't use EmbeddedSolrServer at all.
It is rarely used and there can be hidden things there.
Consider using jetty which is actually tested.
Since you commit every min
One thing to investigate is whether your caches are too large and gradually
filling up memory. It does sound like memory is getting tighter over time.
A memory profiler would be helpful in figuring out memory issues.
Moving to autoCommits would also eliminate any slowness due to overlapping
search
Hi all,
we're using solr in our application and have problem that both searching
and indexing is slowing down over time.
Versions:
-
Java 1.7
Solr 4.7.2
Lucene 4.1 (luceneMatchVersion param in solrconfig.xml)
App architecture:
-
We don't use solr as standalone applicat