'waitFlush' means 'wait until the data from this commit is completely
written to disk'. 'waitSearcher' means 'wait until Solr has
completely finished loading up the new index from what it wrote to
disk'.
Optimize rearranges the entire disk footprint of the disk. It needs a
separate amount of free
Hi there,
Thanks for the reply!
Our backend code is currently set to commit every time it sends over a
batch of documents - so it depends on how big the batch is and how
often edits occur - probably too often. I've looked at the code, and
the SolrJ commit() method takes two parameters - one
How often do you commit? New searchers are only created after a
commit. You notice that handleCommit is in the stack trace :) This
means that commits are happening too often for the amount of other
traffic currently happening, and so it can't finishing creating the
searcher before the next commit s
Hi there,
We have a setup in which our main application (running on a separate Tomcat
instance on the same machine) uses SolrJ calls to an instance of Solr running
on the same box. SolrJ is used both for indexing and searching Solr. Searching
seems to be working fine, but quite frequently we see
