Hi,
I am new to community and thank you for letting me in.
Let me get into my concern real quick. Please find my OS and Solr versions
Ubuntu 14.04.4 LTS
solr-spec 4.10.2
solr-impl 4.10.2 1634293 - mike - 2014-10-26 05:56:21
lucene-spec 4.10.2
lucene-impl 4.10.2 1634293 - mike - 2014-10-26 05:51:56
I am getting the following errors/warnings from Solr
1, ERROR: org.apache.solr.client.solrj.impl.HttpSolrServer$RemoteSolrException:
Error opening new searcher. exceeded limit of maxWarmingSearchers=2,
try again later.
2, PERFORMANCE WARNING: Overlapping onDeckSearchers=2
3, WARN: DistributedUpdateProcessor error sending update
org.apache.solr.client.solrj.impl.HttpSolrServer$RemoteSolrException:
Error opening new searcher. exceeded limit of maxWarmingSearchers=2,
try again later.
I have gone through various discussion threads and was able to get a
minor idea on scenarios where maxWarmingSearchers exceeds. We have
commit doing from application for individual requests and autocommit
enabled.
So my concern is, is there any chance of performance issues when
number of commits are high at a particular point of time. In our
application, we are approximating like 100-500 commits can happen
simultaneously from application and autocommit too for those
individual requests which are not committing individually after the
write.
Autocommit is configured as follows,
<autoCommit>
<maxTime>15000</maxTime>
<openSearcher>false</openSearcher>
</autoCommit>
When worked on the openSearcher parameter, I see it makes solr not to
open a new search while commit is undergoing. How many seconds or
milliseconds, solr takes to complete a commit and allow further new
searches to spawn..? Considering we have a massive numerous individual
commits and massive doc autocommit, is setting up openSearcher to
false, a good practice..? What happens to the new requests when a
commit is going on. Will it be queued for new search to spawn or will
it be delivered with the old search existed..?
Thanks in advance,
Leo Prince.
