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

Reply via email to