Hi Shawn,
Thanks a lot for your nice explanation.. Now I understood the
difference between autoCommit and autoSoftCommit.. Now my config looks like
below.
<autoCommit>
<maxDocs>10000</maxDocs>
<openSearcher>false</openSearcher>
</autoCommit>
<autoSoftCommit>
<maxTime>15000</maxTime>
</autoSoftCommit>
With this now I am getting some other error like this.
org.apache.solr.client.solrj.impl.HttpSolrServer$RemoteSolrException: version
conflict for 1401421678039128128000000030383128128 expected=1469497192978841608
actual=1469497212082847746
What could be the reason?
Thanks & Regards,
Arjun M
-----Original Message-----
From: ext Shawn Heisey [mailto:s...@elyograg.org]
Sent: Thursday, May 29, 2014 10:14 PM
To: solr-user@lucene.apache.org
Subject: Re: Error enquiry- exceeded limit of maxWarmingSearchers=2
On 5/29/2014 7:52 AM, M, Arjun (NSN - IN/Bangalore) wrote:
> Thanks Shawn... Just one more question..
>
> Can both autoCommit and autoSoftCommit be enabled? If both are enabled, which
> one takes precedence?
Yes, and it's a very common configuration. If you do enable both, you
want openSearcher to be false on autoCommit, so that your hard commits
are not making documents visible. That is a job for autoSoftCommit. If
you use openSearcher=false on autoCommit, then the question of which one
takes precendence actually has no meaning, because the two kinds of
commits will be doing different things.
Read this until you completely understand it:
http://searchhub.org/2013/08/23/understanding-transaction-logs-softcommit-and-commit-in-sorlcloud/
Thanks,
Shawn
