Hi Erick

Thanks for your response. I understand your point, but what I was asking was does solr reopen searchers after a commit call even if the commit was called with openSearcher=false since this is what seems to be happening based on these log entries?

Also, it seems that if autocommit is configured with <openSearcher>false</openSearcher> and softAutoCommit is set to -1, absence of any other commit call, the new updates, although committed, would remain invisible forever. my problem here is that I am going for maximum indexing performance, millions of document per each batch job, couple of batch jobs per day. their immediate visibility or even delayed visibility is not a priority, but they have to become visible at some point. preferably at the end of each batch job. what do you think would be the best way to go about this?

thanks,

On 09/20/2017 10:17 AM, Erick Erickson wrote:
First, I would not recommend you call commit from the client. It's
usually far better to let your autocommit settings in solrconfig.xml
deal with it. When you need to search, you either need to configure
<autocommit> with <openSearcher>true</openSearcher>

or set <softAutoCommit> to something other than -1.

https://lucidworks.com/2013/08/23/understanding-transaction-logs-softcommit-and-commit-in-sorlcloud/

Best,
Erick

On Tue, Sep 19, 2017 at 4:53 PM, kaveh minooie <ka...@plutoz.com> wrote:
Hi eveyone

I am trying to figure out why calling commit from my client takes a very
long time in an environment with concurrent updates, and I see the following
snippet in the solr log files when client calls for commit. my question is
regarding the third info. what is it opening? and how can make solr to stop
doing that?


INFO  - 2017-09-19 16:42:20.557; [c:dosweb2016 s:shard2 r:core_node5
x:dosweb2016] org.apache.solr.update.DirectUpdateHandler2; start
commit{,optimize=false,openSearcher=false,waitSearcher=true,expungeDeletes=false,softCommit=false,prepareCommit=false}
INFO  - 2017-09-19 16:42:20.557; [c:dosweb2016 s:shard2 r:core_node5
x:dosweb2016] org.apache.solr.update.SolrIndexWriter; Calling setCommitData
with IW:org.apache.solr.update.SolrIndexWriter@3ee73284
INFO  - 2017-09-19 16:42:20.660; [c:dosweb2016 s:shard2 r:core_node5
x:dosweb2016] org.apache.solr.search.SolrIndexSearcher; Opening
[Searcher@644a8d33[dosweb2016] realtime]
INFO  - 2017-09-19 16:42:20.668; [c:dosweb2016 s:shard2 r:core_node5
x:dosweb2016] org.apache.solr.update.DirectUpdateHandler2; end_commit_flush


thanks,
--
Kaveh Minooie

--
Kaveh Minooie

Reply via email to