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
only trying out these,
>
> • Install a standalone solr 5.3.2 in my PC
> • Indexed some 10 db records
> • Hit core reload/call commit frequently in quick internals
> • Seeing the o.a.s.c.SolrCore [db] PERFORMANCE WARNING: Overlapping
> onDeckSearche
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
o: solr-user@lucene.apache.org
Subject: Re: PERFORMANCE WARNING: Overlapping onDeckSearchers=2
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 colle
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 f
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
al Message-
From: Aswath Srinivasan (TMS) [mailto:aswath.sriniva...@toyota.com]
Sent: Monday, March 21, 2016 11:52 AM
To: solr-user@lucene.apache.org
Subject: PERFORMANCE WARNING: Overlapping onDeckSearchers=2
Fellow developers,
PERFORMANCE WARNING: Overlapping onDeckSearchers=2
I'm seei
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.
In my observation, this WARN comes when I hit frequent hard co
14 5:51 pm
Subject: Re: SOLR Cloud 4.6 - PERFORMANCE WARNING: Overlapping onDeckSearchers=2
On 3/30/2014 2:59 PM, Rishi Easwaran wrote:
> RAM shouldn't be a problem.
> I have a box with 144GB RAM, running 12 instances with 4GB Java heap each.
> There are 9 instances wrting to 1TB of SSD
On 3/30/2014 2:59 PM, Rishi Easwaran wrote:
> RAM shouldn't be a problem.
> I have a box with 144GB RAM, running 12 instances with 4GB Java heap each.
> There are 9 instances wrting to 1TB of SSD disk space.
> Other 3 are writing to SATA drives, and have autosoftcommit disabled.
This brought up
-user
Sent: Fri, Mar 28, 2014 8:35 pm
Subject: Re: SOLR Cloud 4.6 - PERFORMANCE WARNING: Overlapping onDeckSearchers=2
On 3/28/2014 4:07 PM, Rishi Easwaran wrote:
>
> Shawn,
>
> I changed the autoSoftCommit value to 15000 (15 sec).
> My index size is pretty small ~4GB and
On 3/28/2014 4:07 PM, Rishi Easwaran wrote:
>
> Shawn,
>
> I changed the autoSoftCommit value to 15000 (15 sec).
> My index size is pretty small ~4GB and its running on a SSD drive with ~100
> GB space on it.
> Now I see the warn message every 15 seconds.
>
> The caches I think are minimal
>
on SSD drives is a long time to
handle a 4GB index.
Thanks,
Rishi.
-Original Message-
From: Shawn Heisey
To: solr-user
Sent: Fri, Mar 28, 2014 3:28 pm
Subject: Re: SOLR Cloud 4.6 - PERFORMANCE WARNING: Overlapping onDeckSearchers=2
On 3/28/2014 1:03 PM, Rishi Easwaran wrote:
>
And in addition, if you begin to see more onDeckSearchers warming up
simultaneously, just bumping up maxWarmingSearchers is only postponing the
proper core problem solution [1]
We have been through this ourselves!
http://wiki.apache.org/solr/SolrPerformanceProblems#Slow_commits
On Fri, Mar 28,
On 3/28/2014 1:03 PM, Rishi Easwaran wrote:
I thought auto soft commit was for NRT search (shouldn't it be optimized for
search performance), if i have to wait 10 mins how is it NRT? or am I missing
something?
You are correct, but once a second is REALLY often. If the rest of your
config is
02 pm
Subject: Re: SOLR Cloud 4.6 - PERFORMANCE WARNING: Overlapping onDeckSearchers=2
Hi Rishi,
Do you really need soft-commit every second? Can you make it 10 mins, for
example?
What is happening (conditional on checking your logs) is that several
commits (looks like 2 in your case) are arriving
, Rishi Easwaran wrote:
> All,
>
> I am running SOLR Cloud 4.6, everything looks ok, except for this warn
> message constantly in the logs.
>
>
> 2014-03-27 17:09:03,982 WARN [commitScheduler-15-thread-1] [] SolrCore -
> [index_shard16_replica1] PERFORMANCE WARNING: Overl
All,
I am running SOLR Cloud 4.6, everything looks ok, except for this warn message
constantly in the logs.
2014-03-27 17:09:03,982 WARN [commitScheduler-15-thread-1] [] SolrCore -
[index_shard16_replica1] PERFORMANCE WARNING: Overlapping onDeckSearchers=2
2014-03-27 17:09:05,517 WARN
20 matches
Mail list logo
