Hi Kaya,
The answer is simple: as much as your requirements allow delay between data 
being indexed and changes being visible. It is sometimes seconds and sometimes 
hours or even a day is tolerable. On each commit your caches are invalidated 
and warmed (if it is configured like that) so in order to get better use of 
caches, you should commit as rare as possible.

The setting that you provided is about hard commits and those are configured 
not to open new searcher so such commit does not cause “exceeded limit” error. 
You either have soft auto commits configured or you do explicit commits when 
updating documents. Check and tune those and if you do explicit commits, remove 
those if possible. If you cannot afford less frequent commits, you have to tune 
your warming strategy to make sure it does not take as much time as period 
between two commits.

HTH,
Emir
--
Monitoring - Log Management - Alerting - Anomaly Detection
Solr & Elasticsearch Consulting Support Training - http://sematext.com/



> On 26 Feb 2020, at 06:16, Kayak28 <kaya.ota....@gmail.com> wrote:
> 
> Hello, Solr Community:
> 
> Another day, I had an error "exceeded limit of maxWarmingSearchers=2."
> I know this error causes when multiple commits(which opens a new searcher)
> are requested too frequently.
> 
> As far as I read Solr wiki, it recommends for me to have more interval
> between each commit, and make commit frequency less.
> Using autoCommit,  I would like to decrease the commit frequency, but I am
> not sure how much I should increase the value of maxTime in autoCommit?
> 
> My current configuration is the following:
> 
>    <autoCommit>
>      <maxTime>${solr.autoCommit.maxTime:15000}</maxTime>
>      <openSearcher>false</openSearcher>
>    </autoCommit>
> 
> 
> 
> How do you determine how much you increase the value in this case?
> Is there any rule of thumb advice to configure commit frequency?
> 
> Any help will be appreciated.
> 
> Sincerely,
> Kaya Ota

Reply via email to