Re: Does commitWithin override autoSoftCommit?

[Shawn Heisey]

On 7/18/2019 9:37 AM, Benjamin Mellish wrote:
I have a solrconfig.xml file as follows:
<updateHandler class="solr.DirectUpdateHandler2">
     <autoSoftCommit>
         <maxTime>2000</maxTime>
     </autoSoftCommit>
     <autoCommit>
         <maxTime>20000</maxTime>
         <openSearcher>false</openSearcher>
     </autoCommit>
     <updateLog>
         <str name="dir">${solr.ulog.dir:}</str>
     </updateLog>
</updateHandler>

But I also submit records with a 'commitWithin' of 10 seconds. It seems
that my documents are not searchable with the soft commit every second, but
rather with the commitWithin or the hard commit. Is the 'commitWithin'
setting taking precedence over the autoSoftCommit timer?

With this config and a 10 second commitWithin, the autoSoftCommit is 
what will fire first -- two seconds after the first update completes.

It could be that the commit takes so long to complete that it LOOKS like 
it's the larger timeframe.  So if a commit that opens a new searcher 
takes 10 seconds or longer to complete, it will start after two seconds 
(the autoSoftCommit value), but it will take at least 12 seconds total 
for users to actually see the change.

Reducing or eliminating cache warming can help commits to complete 
faster.  Sometimes it is not possible to speed up the soft commit. 
Having low values for autoSoftCommit like two seconds is not recommended.

Thanks,
Shawn