March 22, 2016 10:41 AM
To: solr-user@lucene.apache.org
Subject: Re: PERFORMANCE WARNING: Overlapping onDeckSearchers=2
On 3/22/2016 11:32 AM, Aswath Srinivasan (TMS) wrote:
> Thank you Shawn for taking time and responding.
>
> Unfortunately, this is not the case. My heap is not even going p
On 3/22/2016 11:32 AM, Aswath Srinivasan (TMS) wrote:
> Thank you Shawn for taking time and responding.
>
> Unfortunately, this is not the case. My heap is not even going past 50% and I
> have a heap of 10 GB on a instance that I just installed as a standalone
> version and was only trying out th
u all for spending time on this. I shall post back my findings, if I'm
findings are useful.
Thank you,
Aswath NS
Mobile +1 424 345 5340
Office+1 310 468 6729
-Original Message-
From: Shawn Heisey [mailto:apa...@elyograg.org]
Sent: Monday, March 21, 2016 6:07 PM
To: solr-user@lucene.
On 3/21/2016 6:49 PM, Aswath Srinivasan (TMS) wrote:
>>> Thank you for the responses. Collection crashes as in, I'm unable to open
>>> the core tab in Solr console. Search is not returning. None of the page
>>> opens in solr admin dashboard.
>>>
>>> I do understand how and why this issue occurs a
ion or delete the data folder.
Again, I know how to avoid this issue but if it still happens then what can be
done to avoid a complete reindexing.
Thank you,
Aswath NS
-Original Message-
From: Shawn Heisey [mailto:apa...@elyograg.org]
Sent: Monday, March 21, 2016 4:19 PM
T
On 3/21/2016 12:52 PM, Aswath Srinivasan (TMS) wrote:
> Fellow developers,
>
> PERFORMANCE WARNING: Overlapping onDeckSearchers=2
>
> I'm seeing this warning often and whenever I see this, the collection
> crashes. The only way to overcome this is by deleting the data folder and
> reindexing.
>
>
Sent: Monday, March 21, 2016 2:26 PM
To: solr-user@lucene.apache.org
Subject: RE: PERFORMANCE WARNING: Overlapping onDeckSearchers=2
: What I'm wondering is, what should one do to fix this issue when it
: happens. Is there a way to recover? after the WARN appears.
It's just a warning t
: What I'm wondering is, what should one do to fix this issue when it
: happens. Is there a way to recover? after the WARN appears.
It's just a warning that you have a sub-optimal situation from a
performance standpoint -- either committing too fast, or warming too much.
It's not a failure, a
Please note that I'm not looking to find ways to avoid this issue. There are
lot of internet articles on this topic.
What I'm wondering is, what should one do to fix this issue when it happens. Is
there a way to recover? after the WARN appears.
Thank you,
Aswath NS
-Original Message-
F
