[
https://issues.apache.org/jira/browse/SOLR-13620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn Heisey resolved SOLR-13620.
---------------------------------
Resolution: Invalid
For this project, Jira is not a support portal, it is for bug reports. This is
not a bug.
When you opened this issue, there was bold red text indicating that problems
should be discussed on the mailing list or IRC channel before opening an issue.
I am closing this issue as invalid.
That warning means commits are happening on your index too quickly. The
commits are happening WAY too quickly if you still get the warning with the
maximum warming searchers raised to 16. The fix is to reduce the frequency of
your commits. Such commits may be happening automatically according to Solr's
configuration.
There is more info than you asked for on this blog post:
https://lucidworks.com/post/understanding-transaction-logs-softcommit-and-commit-in-sorlcloud/
If you need further assistance, please bring this issue up on the mailing list
or IRC channel.
> Apache Solr warning on 6.2.1
> ----------------------------
>
> Key: SOLR-13620
> URL: https://issues.apache.org/jira/browse/SOLR-13620
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: clients - php
> Affects Versions: 6.2.1
> Environment: Cent OS 6.10, Apache Solr
> Reporter: Midas Nitin
> Priority: Major
> Labels: performance
> Fix For: 6.2.1
>
>
> Hello,
> We have Apache Solr version 6.2.1 installed on server and we are getting this
> warning on Apache Solr log from few days which has affected performance of
> solr queries and put latency on our App:
> SolrCore [user_details] PERFORMANCE WARNING: Overlapping onDeckSearchers=2
> So we have followed this article
> [https://support.datastax.com/hc/en-us/articles/207690673-FAQ-Solr-logging-PERFORMANCE-WARNING-Overlapping-onDeckSearchers-and-its-meaning]
> and made changes in SolrConfig.xml file of user_details like this:
> <maxWarmingSearchers>16</maxWarmingSearchers>
> and also we have reduced number of autowarmCount
> <cache name="perSegFilter"
> class="solr.search.LRUCache"
> size="10"
> initialSize="0"
> autowarmCount="5"
> regenerator="solr.NoOpRegenerator" />
> however still we are getting this warning. Can you please help us how can we
> improve the performance of solr queries on our app.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
