Re: SOLR PERFORMANCE Warning

[Emir Arnautović]

Hi,
It means that you are either committing too frequently or your warming up takes 
too long. If you are committing on every bulk, stop doing that and use 
autocommit.

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



> On 21 Feb 2020, at 06:54, Akreeti Agarwal  wrote:
> 
> Hi All,
> 
> 
> 
> I am using SOLR 7.5 version with master slave architecture.
> 
> I am getting :
> 
> 
> 
> "PERFORMANCE WARNING: Overlapping onDeckSearchers=2"
> 
> 
> 
> continuously on my master logs for all cores. Please help me to resolve this.
> 
> 
> 
> 
> 
> Thanks & Regards,
> 
> Akreeti Agarwal
> 
> ::DISCLAIMER::
> 
> The contents of this e-mail and any attachment(s) are confidential and 
> intended for the named recipient(s) only. E-mail transmission is not 
> guaranteed to be secure or error-free as information could be intercepted, 
> corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses 
> in transmission. The e mail and its contents (with or without referred 
> errors) shall therefore not attach any liability on the originator or HCL or 
> its affiliates. Views or opinions, if any, presented in this email are solely 
> those of the author and may not necessarily reflect the views or opinions of 
> HCL or its affiliates. Any form of reproduction, dissemination, copying, 
> disclosure, modification, distribution and / or publication of this message 
> without the prior written consent of authorized representative of HCL is 
> strictly prohibited. If you have received this email in error please delete 
> it and notify the sender immediately. Before opening any email and/or 
> attachments, please check them for viruses and other defects.
> 

SOLR PERFORMANCE Warning

[Akreeti Agarwal]

Hi All,



I am using SOLR 7.5 version with master slave architecture.

I am getting :



"PERFORMANCE WARNING: Overlapping onDeckSearchers=2"



continuously on my master logs for all cores. Please help me to resolve this.





Thanks & Regards,

Akreeti Agarwal

::DISCLAIMER::

The contents of this e-mail and any attachment(s) are confidential and intended 
for the named recipient(s) only. E-mail transmission is not guaranteed to be 
secure or error-free as information could be intercepted, corrupted, lost, 
destroyed, arrive late or incomplete, or may contain viruses in transmission. 
The e mail and its contents (with or without referred errors) shall therefore 
not attach any liability on the originator or HCL or its affiliates. Views or 
opinions, if any, presented in this email are solely those of the author and 
may not necessarily reflect the views or opinions of HCL or its affiliates. Any 
form of reproduction, dissemination, copying, disclosure, modification, 
distribution and / or publication of this message without the prior written 
consent of authorized representative of HCL is strictly prohibited. If you have 
received this email in error please delete it and notify the sender 
immediately. Before opening any email and/or attachments, please check them for 
viruses and other defects.

RE: solr | performance warning

[Prateek Jain J]

Thanks EricK


Regards,
Prateek Jain

-Original Message-
From: Erick Erickson [mailto:erickerick...@gmail.com] 
Sent: 21 November 2016 04:32 PM
To: solr-user <solr-user@lucene.apache.org>
Subject: Re: solr | performance warning

_when_ are you seeing this? I see this on startup upon occasion, and I _think_ 
there's a JIRA about startup opening more than one searcher on startup.
If it _is_ on startup, you can simply ignore it.

If it's after the system is up and running, then you're probably committing too 
frequently. "Too frequently" means your autowarm interval is longer than your 
commit interval. It's usually best to just let autocommit handle this BTW.

This is totally on a per-core basis. You won't get this warning if you commit 
to coreA and coreB simultaneously, only if you commit to an individual core too 
frequently.

Best,
Erick

On Mon, Nov 21, 2016 at 7:47 AM, Prateek Jain J <prateek.j.j...@ericsson.com> 
wrote:
>
> Hi All,
>
> I am observing following error in logs, any clues about this:
>
> 2016-11-06T23:15:53.066069+00:00@solr@@ 
> org.apache.solr.core.SolrCore:1650 - [my_custom_core] PERFORMANCE 
> WARNING: Overlapping onDeckSearchers=2
>
> Slight web search suggests that it could be a case of too-frequent commits. I 
> have multiple cores running in solr, so one or the other would be commiting 
> at some time. Any clues/pointers/suggestions?
>
> I am using solr 4.8.1.
>
> Regards,
> Prateek Jain
>

Re: solr | performance warning

[Erick Erickson]

_when_ are you seeing this? I see this on startup upon occasion, and I _think_
there's a JIRA about startup opening more than one searcher on startup.
If it _is_ on startup, you can simply ignore it.

If it's after the system is up and running, then you're probably committing too
frequently. "Too frequently" means your autowarm interval is longer than
your commit interval. It's usually best to just let autocommit handle this BTW.

This is totally on a per-core basis. You won't get this warning if you commit
to coreA and coreB simultaneously, only if you commit to an individual core
too frequently.

Best,
Erick

On Mon, Nov 21, 2016 at 7:47 AM, Prateek Jain J
 wrote:
>
> Hi All,
>
> I am observing following error in logs, any clues about this:
>
> 2016-11-06T23:15:53.066069+00:00@solr@@ org.apache.solr.core.SolrCore:1650 - 
> [my_custom_core] PERFORMANCE WARNING: Overlapping onDeckSearchers=2
>
> Slight web search suggests that it could be a case of too-frequent commits. I 
> have multiple cores running in solr, so one or the other would be commiting 
> at some time. Any clues/pointers/suggestions?
>
> I am using solr 4.8.1.
>
> Regards,
> Prateek Jain
>

solr | performance warning

[Prateek Jain J]

Hi All,

I am observing following error in logs, any clues about this:

2016-11-06T23:15:53.066069+00:00@solr@@ org.apache.solr.core.SolrCore:1650 - 
[my_custom_core] PERFORMANCE WARNING: Overlapping onDeckSearchers=2

Slight web search suggests that it could be a case of too-frequent commits. I 
have multiple cores running in solr, so one or the other would be commiting at 
some time. Any clues/pointers/suggestions?

I am using solr 4.8.1.

Regards,
Prateek Jain