I am on 4.2.1
@Yonik Seeley I do understand the cost and run it once per 24 hours and
perhaps later this interval will be increased up to a few days.
In general I am optimizing not to merge the fragments but to remove deleted
docs. My index refreshes quickly and number of deleted docs could reach
is
really absolutely needed.
3. Try to understand why #1 is not sufficient and resolve the cause(s), so
that optimize is no longer needed.
-- Jack Krupansky
-Original Message-
From: Yonik Seeley
Sent: Monday, May 27, 2013 9:46 AM
To: solr-user@lucene.apache.org
Subject: Re: Overlapp
similarity uses
maxDoc for IDF.
The cost is also much lower when using SSD's, forceMerging a 1GB core is a
matter of seconds.
-Original message-
> From:Yonik Seeley
> Sent: Mon 27-May-2013 15:47
> To: solr-user@lucene.apache.org
> Subject: Re: Overlapping onDeckSearch
On Mon, May 27, 2013 at 7:11 AM, Jack Krupansky wrote:
> The intent is that optimize is obsolete and should no longer be used
That's incorrect.
People need to understand the cost of optimize, and that it's use is optional.
It's up to the developer to figure out of the benefits of calling
optimiz
: Monday, May 27, 2013 3:51 AM
To: solr-user@lucene.apache.org
Subject: Re: Overlapping onDeckSearchers=2
Hi, thanks for the response. Seems like this is the case because there are
no
any other applications that could fire commit/optimize calls. All commits
are triggered by Solr and the optimize is
Hi, thanks for the response. Seems like this is the case because there are no
any other applications that could fire commit/optimize calls. All commits
are triggered by Solr and the optimize is triggered by a cron task.
Because of all that it looks like a bug in Solr. It probably should not run
co
This can happen if an auto commit overlaps with the optimize command too.
On Sat, May 25, 2013 at 5:26 PM, heaven wrote:
> Hi, I am getting this warning with auto commits. My application does not
> send
> commits. I am optimizing the index once per day and seems like this warning
> appear every
Hi, I am getting this warning with auto commits. My application does not send
commits. I am optimizing the index once per day and seems like this warning
appear every time the optimization process is launched.
Best,
Alex
--
View this message in context:
http://lucene.472066.n3.nabble.com/Overl
The commit happens (twice!) causing potentially double the RAM to be
used for warming two index searchers, one of which will be thrown away
right after warming. It's best to avoid overlapping these warming
searchers. Using Solr's autocommit capability is the easiest way to
manage the sit
Thanks for the repsonse .What happens in this scenario?
Does the commit happen in this case or does the search server hang or just
throws an error without committing
Regards
Sujatha
On Mon, May 3, 2010 at 11:41 PM, Chris Hostetter
wrote:
> : When i run 2 -3 commits parallely to diff instances
: When i run 2 -3 commits parallely to diff instances or same instance I get
: this error
:
: PERFORMANCE WARNING: Overlapping onDeckSearchers=2
:
: What is the Best approach to solve this
http://wiki.apache.org/solr/FAQ#What_does_.22PERFORMANCE_WARNING:_Overlapping_onDeckSearchers.3DX.22_mean_
On Mon, May 3, 2010 at 11:24 AM, revas wrote:
> Hello,
>
> We have a server with many solr instances running (around 40-50) .
>
> We are committing documents ,sometimes one or sometimes around 200
> documents at a time .to only one instance at a time
>
> When i run 2 -3 commits parallely to
12 matches
Mail list logo
