Hello,
We're using solr 1.2 and a nightly build of the solrj client code. We very
occasionally see things like this:
org.apache.solr.client.solrj.SolrServerException: Error executing query
at org.apache.solr.client.solrj.request.QueryRequest.process(
QueryRequest.java:86)
at org.apache.solr.client.solrj.impl.BaseSolrServer.query(
BaseSolrServer.java:99)
...
Caused by: org.apache.solr.common.SolrException: Internal Server Error
I'm guessing that this might be due to solr being in the middle of a commit
or optimize. Could solr throw an exception like that in this case?
We also occasionally see solr taking too long to respond. We currently make
our commit/optimize calls without any arguments. I'm wondering whether
setting waitSearcher="false" might allow search queries to be served while a
commit/optimize is being run. I found this in an old message from this
list:
> Yes, it looks like there is no difference... the code to make commit
> totally asynchronous was never put in (so you can't really get commit
> to return instantly, it will always wait until the IndexWriter is closed).
This isn't a problem for us as the thread making the commit/optimize call is
separate from thread(s) making queries. Is waitSearcher="false" designed to
allow queries to be processed while a commit/optimize is being run? Are
there any negative side effects to this setting (other than a query being
slightly out-of-date :)?
Thanks,
Jason
