On 11/20/2015 12:33 AM, Midas A wrote:
> As we are this server as a master server there are no queries running on
> it . in that case should i remove these configuration from config file .
The following cache info says that there ARE queries being run on this
server:
> QueryResultCache:
>
> lo
Hi,
Since this is master node, and not expected to have queries, you can
disable caches completely. However, from numbers cache autowarm is not
an issue here but probably frequency of commits and/or warmup queries.
How do you do commits? Since master-slave, I don't see reason to have
them too
thanks Shawn,
As we are this server as a master server there are no queries running on
it . in that case should i remove these configuration from config file .
Total Docs: 40 0
Stats
#
Document cache :
lookups:823
hits:4
hitratio:0.00
inserts:820
evictions:0
size:820
warmupTime:0
cumulati
On 11/19/2015 11:06 PM, Midas A wrote:
> autowarmCount="1000"/> size="1000" initialSize="1000" autowarmCount="1000"/> ="1000" autowarmCount="1000"/>
Your caches are quite large. More importantly, your autowarmCount is
very large. How many documents are in each of your cores? If you check
t
Thanks Emir ,
So what we need to do to resolve this issue .
This is my solr configuration. what changes should i do to avoid the
warning .
~abhishek
On Thu, Nov 19, 2015 at 6:37 PM, Emir Arnautovic <
emir.arnauto...@sematext.com> wrote:
> This means that one searcher is still warming
This means that one searcher is still warming when other searcher
created due to commit with openSearcher=true. This can be due to
frequent commits of searcher warmup taking too long.
Emir
--
Monitoring * Alerting * Anomaly Detection * Centralized Log Management
Solr & Elasticsearch Support *
Getting following log on solr
PERFORMANCE WARNING: Overlapping onDeckSearchers=2`
